Triple
T9331252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridge of Lions |
E224526
|
entity |
| Predicate | temporaryBridgeInUse |
P72280
|
FINISHED |
| Object | 2006–2010 |
—
|
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: 2006–2010 | Statement: [Bridge of Lions, temporaryBridgeInUse, 2006–2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporaryBridgeInUse Context triple: [Bridge of Lions, temporaryBridgeInUse, 2006–2010]
-
A.
bridgeUsed
Indicates that a bridge is utilized or traversed by an entity to cross between two locations or points.
-
B.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
C.
hasNearbyBridge
Indicates that one entity is located close to a bridge associated with or relevant to it.
-
D.
bridgeLocation
Indicates the specific place or area where a bridge is situated or spans.
-
E.
bridgeStatus
chosen
Indicates the current operational condition or availability state of a bridge (e.g., open, closed, restricted).
- 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_69ca8427a0c08190b749831d5ea98f02 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd37ae4fcc81909be75d51e2dc455d |
completed | April 1, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cc7a643924819097f01144734901cf |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:39 p.m.