Triple
T26144534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-30 Trinity River Bridge |
E659617
|
entity |
| Predicate | crossesWaterbody |
P15424
|
FINISHED |
| Object | Trinity River in Dallas |
—
|
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: Trinity River in Dallas | Statement: [I-30 Trinity River Bridge, crossesWaterbody, Trinity River in Dallas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossesWaterbody Context triple: [I-30 Trinity River Bridge, crossesWaterbody, Trinity River in Dallas]
-
A.
crossesWaterBody
chosen
Indicates that an entity moves from one side of a water body to the other by passing over, through, or across it.
-
B.
waterwayTypeCrossed
Indicates the specific kind of waterway (e.g., river, canal, stream) that is being crossed in the described relationship or action.
-
C.
crossedByRiver
Indicates that a river passes across or through a specified area, feature, or route.
-
D.
crossesWatershed
Indicates that one entity passes from one drainage basin or watershed area into another, traversing the boundary between them.
-
E.
acrossWaterFrom
Indicates that two entities are located on opposite sides of a body of water, separated by that water.
- 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_69ee5bc496a88190af7deb7ab5e081de |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 26, 2026, 8:21 p.m.