Triple
T18986115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montijo |
E464562
|
entity |
| Predicate | hasBridgeAccessVia |
P14516
|
FINISHED |
| Object | Vasco da Gama Bridge vicinity |
—
|
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: Vasco da Gama Bridge vicinity | Statement: [Montijo, hasBridgeAccessVia, Vasco da Gama Bridge vicinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBridgeAccessVia Context triple: [Montijo, hasBridgeAccessVia, Vasco da Gama Bridge vicinity]
-
A.
hasBridgeAccess
chosen
Indicates that an entity is permitted to enter or use a specific bridge or bridge-controlled area.
-
B.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
C.
hasBridgeLayer
Indicates that one entity includes or is associated with a specific bridge layer within its structure or configuration.
-
D.
hasBridges
Indicates that one entity possesses, contains, or is characterized by one or more bridges connecting locations or components.
-
E.
hasInternationalBridgeTo
Indicates a relationship where two locations are directly connected by a bridge that crosses an international border between them.
- 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d65f7f08819088f56e8e030851b1 |
completed | April 20, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.