Triple
T18848306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fertagus cross-Tagus rail |
E460973
|
entity |
| Predicate | bridgeDeck |
P106503
|
FINISHED |
| Object | lower deck of 25 de Abril Bridge |
—
|
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: lower deck of 25 de Abril Bridge | Statement: [Fertagus cross-Tagus rail, bridgeDeck, lower deck of 25 de Abril Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeDeck Context triple: [Fertagus cross-Tagus rail, bridgeDeck, lower deck of 25 de Abril Bridge]
-
A.
bridgeDeckType
Indicates the structural or material type of deck used in a bridge.
-
B.
bridgeStructure
Indicates a structural relationship where one entity functions as a bridge that spans or connects two separate points or areas.
-
C.
bridgeType
Indicates the specific kind or classification of a bridge associated with an entity.
-
D.
bridgeCarries
Indicates that a bridge serves as a route or support structure for transporting or conveying something (such as vehicles, pedestrians, or utilities) across an obstacle.
-
E.
bridgeComponent
chosen
Indicates that one entity functions as a structural or functional component of a bridge associated with another entity.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8f079b881908759135c5e2619ee |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.