Triple
T22157935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarim Desert Highway |
E547589
|
entity |
| Predicate | hasRoadsideShelterbelts |
P147197
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tarim Desert Highway, hasRoadsideShelterbelts, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadsideShelterbelts Context triple: [Tarim Desert Highway, hasRoadsideShelterbelts, yes]
-
A.
hasRoadsideFacility
Indicates that a location or route segment is associated with a facility or service situated along its roadside.
-
B.
hasRoadBoundary
Indicates that a road segment is associated with a specific boundary or edge that defines its lateral limits.
-
C.
isRoadless
Indicates that an area or region lacks constructed roads or vehicular access routes.
-
D.
hasBorderWallOrFence
Indicates that a physical barrier such as a wall or fence exists along the border between two entities.
-
E.
hasRoadWidth
Indicates the width measurement of a road segment or roadway in the relationship.
- 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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12a2aadb48190b4d739d1df9529db |
completed | April 28, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e7222d208c819098b12c13e31af629 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:33 p.m.