Triple
T34976949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isla de los Faisanes del Bidasoa |
E1008702
|
entity |
| Predicate | administrationFromSpanishSide |
P195737
|
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: [Isla de los Faisanes del Bidasoa, administrationFromSpanishSide, Irun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrationFromSpanishSide Context triple: [Isla de los Faisanes del Bidasoa, administrationFromSpanishSide, Irun]
-
A.
spanishReturn
Indicates a situation in which something or someone goes back or is sent back in a Spanish context, manner, or language.
-
B.
statusInSpain
Indicates the legal, social, or official condition or standing that an entity has within the jurisdiction of Spain.
-
C.
SPAN-A
Indicates a generic span or interval relationship connecting two elements across a continuous range or segment.
-
D.
SPAN-E
Indicates a relationship where one entity extends over, covers, or bridges across another entity or a specified interval in space, time, or sequence.
-
E.
returnToSpain
Indicates that an entity goes back to Spain, typically after having been away.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
| PDg | Predicate description generation | batch_69fde49953c481909ac352ab36fa9ff2 |
completed | May 8, 2026, 1:26 p.m. |
Created at: May 3, 2026, 4:01 p.m.