Triple
T30272122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Bridge |
E769830
|
entity |
| Predicate | worldRankingByMainSpan |
P41916
|
FINISHED |
| Object | among longest suspension bridges |
—
|
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: among longest suspension bridges | Statement: [East Bridge, worldRankingByMainSpan, among longest suspension bridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldRankingByMainSpan Context triple: [East Bridge, worldRankingByMainSpan, among longest suspension bridges]
-
A.
rankInNorwayByMainSpan
Indicates the position of an entity in an ordered list of entities in Norway, ranked specifically by the length of their main span.
-
B.
bridgeSpans
Indicates that a bridge extends across and connects two separate points or areas.
-
C.
wasWorldsLongestSuspensionBridgeSpan
chosen
Indicates that something held the record for having the longest main span of any suspension bridge in the world at a given time.
-
D.
hasNumberOfMainBridges
Indicates the quantity of primary or main bridges associated with a given entity.
-
E.
wasWorldsHighestBridgeFrom
Indicates that a bridge held the record as the world’s highest bridge starting from a specified time or date.
- 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_69f224856d9881908c7f0dd64f059672 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: April 29, 2026, 7:44 p.m.