Triple
T34975694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridge II |
E1008669
|
entity |
| Predicate | hasDirectionNorthTerminus |
P69344
|
FINISHED |
| Object | Laredo, Texas |
—
|
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: Laredo, Texas | Statement: [Bridge II, hasDirectionNorthTerminus, Laredo, Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectionNorthTerminus Context triple: [Bridge II, hasDirectionNorthTerminus, Laredo, Texas]
-
A.
terminusDirection
Indicates the directional orientation or endpoint direction associated with a route, path, or line.
-
B.
northernDirection
Indicates a spatial relationship where one entity is located to the north of another entity.
-
C.
northernTerminusConnects
chosen
Indicates that a route, line, or pathway connects to or ends at a specified location at its northernmost terminus.
-
D.
northernTerminusVariant
Indicates that one location or feature serves as an alternative or variant northern endpoint of a route, line, or path.
-
E.
direction2Terminus
Indicates the direction in which something leads toward or ends at a particular terminus or endpoint.
- 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_69f76dc78a308190a1ac29ad4a9a4895 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: May 3, 2026, 4:01 p.m.