Triple
T30799968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navarrese–Lapurdian Basque |
E784336
|
entity |
| Predicate | isNonIndoEuropean |
P15732
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Navarrese–Lapurdian Basque, isNonIndoEuropean, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonIndoEuropean Context triple: [Navarrese–Lapurdian Basque, isNonIndoEuropean, true]
-
A.
isNotIndoEuropean
chosen
Indicates that an entity’s language or linguistic affiliation does not belong to the Indo-European language family.
-
B.
areNonAustronesian
Indicates that the entities do not belong to or are not classified within the Austronesian language (or cultural-linguistic) family.
-
C.
isNonEndonymFor
Indicates that a given name for a place, people, or language is used by outsiders and is not the name used by the group or locale itself.
-
D.
identifiedAsIndoEuropeanBy
Indicates that an entity has been classified or recognized as Indo-European by a specified source or agent.
-
E.
isIndigenousLanguageNameOf
Indicates that a given name is the name of a language as expressed in an indigenous language.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:42 p.m.