Triple
T12796118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gladesville Bridge |
E305892
|
entity |
| Predicate | wasWorldsLongestConcreteArchSpan |
P106443
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Gladesville Bridge, wasWorldsLongestConcreteArchSpan, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasWorldsLongestConcreteArchSpan Context triple: [Gladesville Bridge, wasWorldsLongestConcreteArchSpan, true]
-
A.
wasWorldsLongestSuspensionBridgeSpan
Indicates that something held the record for having the longest main span of any suspension bridge in the world at a given time.
-
B.
wasWorldsLongestCableStayedBridgeAtOpening
Indicates that the bridge held the record as the world’s longest cable-stayed bridge at the time it was opened.
-
C.
bridgeSpans
Indicates that a bridge extends across and connects two separate points or areas.
-
D.
isOldestSurvivingBridgeAcross
Indicates that a bridge is the most ancient still-existing bridge that spans a specified waterway, road, or gap.
-
E.
wasLongestBridgeInSoutheastAsiaUntil
Indicates that a bridge held the status of being the longest in Southeast Asia up to a specified point in time.
- F. None of above. chosen
Provenance (4 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e6db68481909a2ca8da1287f3e0 |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d88be0481908c311f1e71b61e70 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:30 p.m.