Triple
T25103880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portugalete |
E628814
|
entity |
| Predicate | bridgeTypeAtVizcayaBridge |
P1787
|
FINISHED |
| Object | transporter 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: transporter bridge | Statement: [Portugalete, bridgeTypeAtVizcayaBridge, transporter bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeTypeAtVizcayaBridge Context triple: [Portugalete, bridgeTypeAtVizcayaBridge, transporter bridge]
-
A.
bridgeType
chosen
Indicates the specific kind or classification of a bridge associated with an entity.
-
B.
bridgeStructure
Indicates a structural relationship where one entity functions as a bridge that spans or connects two separate points or areas.
-
C.
coveredBridgeBuilt
Indicates that a covered bridge was constructed or brought into existence.
-
D.
VictoriaBridgeLocation
Indicates that a specified place or structure is the geographic location of the Victoria Bridge.
-
E.
skybridgeHeight
Indicates the vertical distance or clearance between a skybridge and a reference surface (such as the ground or roadway) or between connected structures.
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f4656bddb4819088650eefd5ef837a |
completed | May 1, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:26 a.m.