Triple
T14800293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Level Bridge |
E347887
|
entity |
| Predicate | lowerDeckUse |
P68896
|
FINISHED |
| Object | road |
—
|
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: road | Statement: [High Level Bridge, lowerDeckUse, road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerDeckUse Context triple: [High Level Bridge, lowerDeckUse, road]
-
A.
lowerDeckDirection
Indicates the direction or orientation associated with movement or positioning on the lower deck of a structure or vehicle.
-
B.
hasLowerDeckFunction
chosen
Indicates that an entity serves a specific role or performs a designated function on the lower deck of a structure or vehicle.
-
C.
lowerDeckCargoPositions
Indicates the specific locations or slots designated for storing cargo in the lower deck area.
-
D.
upperDeckUsedFor
Indicates that the upper deck of an object or structure is utilized for a specified purpose or activity.
-
E.
lowerLevelUsedFor
Indicates that a lower-level component, resource, or abstraction is utilized to implement, support, or realize the functionality of a higher-level one.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decd62c36c81909c2993dc7d1a79ea |
completed | April 14, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.