Triple
T25880384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tianjin–Pukou Railway |
E652029
|
entity |
| Predicate | crossesRiverByFerry |
P152288
|
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: [Tianjin–Pukou Railway, crossesRiverByFerry, Yangtze River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossesRiverByFerry Context triple: [Tianjin–Pukou Railway, crossesRiverByFerry, Yangtze River]
-
A.
bodyOfWaterCrossedByFerry
chosen
Indicates that a body of water is traversed or crossed by a ferry service.
-
B.
crossedByRiver
Indicates that a river passes across or through a specified area, feature, or route.
-
C.
hasRiverCrossingNearby
Indicates that there is a river crossing located in close proximity to the referenced entity or location.
-
D.
hasRiverCrossingType
Indicates the type or nature of a river crossing associated with an entity (e.g., bridge, ford, ferry).
-
E.
crossesWaterBody
Indicates that an entity moves from one side of a water body to the other by passing over, through, or across it.
- F. None of above.
Provenance (3 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_69e7ab3b92cc81908febd90317862647 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6033e7ea4819097fd0c5f651b7a40 |
completed | May 2, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 22, 2026, 8:16 a.m.