Triple
T32233483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G40 Shanghai–Xi'an Expressway |
E823401
|
entity |
| Predicate | passesOverRiver |
P180071
|
FINISHED |
| Object | Yangtze River |
—
|
NE NERFINISHED |
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: Yangtze River | Statement: [G40 Shanghai–Xi'an Expressway, passesOverRiver, Yangtze River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passesOverRiver Context triple: [G40 Shanghai–Xi'an Expressway, passesOverRiver, Yangtze River]
-
A.
crossedByRiver
Indicates that a river passes across or through a specified area, feature, or route.
-
B.
reachedRiver
Indicates that an entity has arrived at or come into contact with a river as a result of movement or travel.
-
C.
hasRiverCrossingType
Indicates the type or nature of a river crossing associated with an entity (e.g., bridge, ford, ferry).
-
D.
acrossWaterFrom
Indicates that two entities are located on opposite sides of a body of water, separated by that water.
-
E.
hasRiverCrossingNearby
Indicates that there is a river crossing located in close proximity to the referenced entity or location.
- 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
| PDg | Predicate description generation | batch_69f730890a008190a882f7828f1c9162 |
completed | May 3, 2026, 11:24 a.m. |
Created at: May 1, 2026, 12:39 a.m.