Triple
T36570250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laira Bridge |
E902100
|
entity |
| Predicate | hasSpanFunction |
P198002
|
FINISHED |
| Object | to carry rail traffic over tidal river |
—
|
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: to carry rail traffic over tidal river | Statement: [Laira Bridge, hasSpanFunction, to carry rail traffic over tidal river]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpanFunction Context triple: [Laira Bridge, hasSpanFunction, to carry rail traffic over tidal river]
-
A.
isSpanning
Indicates that one entity extends across, covers, or bridges the full width, extent, or duration of another entity.
-
B.
hasNavigationSpan
Indicates that one entity includes or is associated with a specific navigational range or segment used for movement or routing.
-
C.
hasApproachSpans
Indicates that one structure or element includes or is associated with approach spans leading into or out of it.
-
D.
hasMainSpanLength
Indicates the relationship specifying the primary or main span’s length associated with an entity.
-
E.
hasChainFunction
Indicates that an entity possesses or is associated with a specific function or role within a chain or sequence of operations.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
| PDg | Predicate description generation | batch_69fec00e5c1c819083d174bb4bc35f29 |
completed | May 9, 2026, 5:03 a.m. |
Created at: May 3, 2026, 4:11 p.m.