Triple
T24991025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chitkul |
E625447
|
entity |
| Predicate | hasBorderRoadsOrganizationPost |
P157515
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: true | Statement: [Chitkul, hasBorderRoadsOrganizationPost, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderRoadsOrganizationPost Context triple: [Chitkul, hasBorderRoadsOrganizationPost, true]
-
A.
hasRoadBoundary
Indicates that a road segment is associated with a specific boundary or edge that defines its lateral limits.
-
B.
belongsToOrganizationBorder
Indicates that an entity is associated with or falls within the jurisdictional boundary of a specific organization.
-
C.
hasRoads
Indicates that there exist constructed road connections linking the related entities.
-
D.
bordersEntity
Indicates that one entity shares a common boundary or border with another entity.
-
E.
bordersEntityType
Indicates that one entity shares a boundary or border with another entity of a specified type.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44a457a888190beb43ff433b12abb |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:03 a.m.