Triple
T25343678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santiago Bridge (Irun) |
E635482
|
entity |
| Predicate | isInBorderTown |
P158224
|
FINISHED |
| Object | Irun |
—
|
NE NERFINISHED |
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: Irun | Statement: [Santiago Bridge (Irun), isInBorderTown, Irun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInBorderTown Context triple: [Santiago Bridge (Irun), isInBorderTown, Irun]
-
A.
hasBorderTownRole
Indicates that an entity serves in an official capacity or role specifically related to a town located on or near a border.
-
B.
hasBorderCity
Indicates that one location is a city situated on or very near the border of another geographic or political region.
-
C.
locatedNearStateBorderWith
Indicates that one entity is situated geographically close to the border of a specified state.
-
D.
hasBorderTownOnCanadianSide
Indicates that one location has a corresponding border town situated on the Canadian side of an international boundary.
-
E.
cityIsBorderCity
Indicates that a city is located on or near a boundary between two regions, countries, or administrative areas.
- F. None of above. chosen
Provenance (4 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f498b936f08190b750199798e9effc |
completed | May 1, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 21, 2026, 1:32 p.m.