Triple
T21312333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autostrada A26 |
E525372
|
entity |
| Predicate | hasBridgeOrTunnelSections |
P26674
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Autostrada A26, hasBridgeOrTunnelSections, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBridgeOrTunnelSections Context triple: [Autostrada A26, hasBridgeOrTunnelSections, yes]
-
A.
hasBridgeAndTunnelStructures
Indicates that there exist both bridge and tunnel structures associated with or connecting the related entities.
-
B.
hasBridgeTunnel
chosen
Indicates that there exists a bridge or tunnel connection between two locations or structures.
-
C.
hasBridgeSection
Indicates that one entity includes or is associated with a specific bridge section as a distinct part or component.
-
D.
hasBridgeUnderpasses
Indicates that one structure, typically a bridge, includes or provides underpasses that allow passage beneath it.
-
E.
hasTunnelSections
Indicates that an entity includes or is composed of multiple distinct tunnel segments or portions.
- 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_69e0b518b8948190ad69cf9a8784d397 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75dca66ac8190a5f0a372a9bc25a7 |
completed | April 21, 2026, 11:21 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:25 p.m.