Triple
T34976948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isla de los Faisanes del Bidasoa |
E1008702
|
entity |
| Predicate | administrationFromFrenchSide |
P11466
|
FINISHED |
| Object | Hendaye |
—
|
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: Hendaye | Statement: [Isla de los Faisanes del Bidasoa, administrationFromFrenchSide, Hendaye]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrationFromFrenchSide Context triple: [Isla de los Faisanes del Bidasoa, administrationFromFrenchSide, Hendaye]
-
A.
usesPrimaryFrenchGateway
Indicates that an entity routes its primary communications or connections through a main gateway located in or associated with French infrastructure or networks.
-
B.
hasFrenchSector
chosen
Indicates that an entity includes, controls, or is associated with a sector or area designated as French.
-
C.
principalFrenchRepresentative
Indicates that one entity serves as the primary official representative of France in relation to another entity.
-
D.
recognizedAsFrenchBy
Indicates that an entity is regarded or acknowledged as French by a specified agent or group.
-
E.
reservedToFrance
Indicates that something is exclusively allocated or designated for France.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: May 3, 2026, 4:01 p.m.