Triple
T8588138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leguan bridge-layer |
E203358
|
entity |
| Predicate | bridgeLengthOptions |
P46595
|
FINISHED |
| Object | approximately 26-meter bridge configuration in some variants |
—
|
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: approximately 26-meter bridge configuration in some variants | Statement: [Leguan bridge-layer, bridgeLengthOptions, approximately 26-meter bridge configuration in some variants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeLengthOptions Context triple: [Leguan bridge-layer, bridgeLengthOptions, approximately 26-meter bridge configuration in some variants]
-
A.
bridgeLength
chosen
Indicates the physical length or span of a bridge structure.
-
B.
bridgeSpans
Indicates that a bridge extends across and connects two separate points or areas.
-
C.
bridgeType
Indicates the specific kind or classification of a bridge associated with an entity.
-
D.
hasSkyBridgeLength
Indicates the length measurement of a sky bridge connecting two structures or areas.
-
E.
bridgeName
Indicates the designated name assigned to a specific bridge.
- 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_69ca8329bb7c8190a63c643730839103 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46c5e8888190b721e791c449b0df |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454504448190aaad2af8b17357cd |
completed | March 31, 2026, 10:05 p.m. |
Created at: March 30, 2026, 6:23 p.m.