Triple
T15431976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sixth Street Viaduct |
E369661
|
entity |
| Predicate | previousBridgeInstanceOf |
P23899
|
FINISHED |
| Object | concrete viaduct |
—
|
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: concrete viaduct | Statement: [Sixth Street Viaduct, previousBridgeInstanceOf, concrete viaduct]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousBridgeInstanceOf Context triple: [Sixth Street Viaduct, previousBridgeInstanceOf, concrete viaduct]
-
A.
originalBridgeRenamed
Indicates that a bridge has undergone a name change from its original designation to a new one.
-
B.
previousInstanceOf
chosen
Indicates that one entity is an earlier occurrence or version of another entity in a sequence or history.
-
C.
bridgeReplaced
Indicates that one bridge has been substituted or exchanged for another, typically as a result of construction, repair, or upgrade.
-
D.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
E.
bridgeType
Indicates the specific kind or classification of a bridge associated with an entity.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03eda01cc8190843e23b260b8503c |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:21 a.m.