Triple
T8865860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alex Fraser Bridge |
E211015
|
entity |
| Predicate | hasDeckWidth |
P3989
|
FINISHED |
| Object | 32 metres |
—
|
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: 32 metres | Statement: [Alex Fraser Bridge, hasDeckWidth, 32 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeckWidth Context triple: [Alex Fraser Bridge, hasDeckWidth, 32 metres]
-
A.
hasDeckType
Indicates that an entity possesses or is associated with a specific type or category of deck.
-
B.
hasWidth
chosen
Indicates that an entity possesses a specific measurement or extent along its width dimension.
-
C.
hasVehicleDeck
Indicates that something (typically a vessel or structure) includes a dedicated deck or level designed for carrying or transporting vehicles.
-
D.
isThroughDeck
Indicates that one object passes completely through another object or surface, extending from one side to the other.
-
E.
hasRailWidth
Indicates that one entity has a specified width measurement for its rail or rails.
- 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_69ca838d3c7c8190a849566d5afd2b11 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6106d41081909db710bda8aaf6fd |
completed | April 1, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69cc5c279ea481908c71756f694b66bf |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:51 p.m.