Triple
T24619192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iruña |
E609355
|
entity |
| Predicate | BasqueDemonym |
P17751
|
FINISHED |
| Object | iruindar |
—
|
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: iruindar | Statement: [Iruña, BasqueDemonym, iruindar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BasqueDemonym Context triple: [Iruña, BasqueDemonym, iruindar]
-
A.
hasBasqueName
chosen
Indicates that an entity is associated with a name expressed in the Basque language.
-
B.
ethnonymAttestedIn
Indicates that the name of an ethnic group (ethnonym) is documented or recorded in a specified source, context, or medium.
-
C.
hasBalearicName
Indicates that an entity is associated with a specific name in the Balearic (Balearic Catalan) language.
-
D.
ethnonymLanguageFamily
Indicates a relationship where an ethnonym is associated with the language family traditionally spoken or linked to that ethnic group.
-
E.
usesDemonymForm
Indicates that one entity refers to another using a demonym form, i.e., a name derived from the inhabitants or nationality associated with that entity.
- 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_69e2c4d1140081909c58667bf68f80c3 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:32 a.m.