Triple
T25038473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lower Navarre |
E627044
|
entity |
| Predicate | hasBasqueDialect |
P28812
|
FINISHED |
| Object | Low Navarrese Basque |
—
|
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: Low Navarrese Basque | Statement: [Lower Navarre, hasBasqueDialect, Low Navarrese Basque]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBasqueDialect Context triple: [Lower Navarre, hasBasqueDialect, Low Navarrese Basque]
-
A.
hasBasqueName
Indicates that an entity is associated with a name expressed in the Basque language.
-
B.
hasDialectalCounterpart
Indicates that one linguistic form has a corresponding equivalent or variant in another dialect.
-
C.
isDialectalBaseOf
Indicates that one language variety serves as the primary dialectal source or foundation from which another dialect develops or is derived.
-
D.
hasPrimaryLanguageDialect
Indicates that an entity’s main or default language is a specific dialect of a broader language.
-
E.
hasTraditionalDialect
chosen
Indicates that an entity possesses or is associated with a traditional form or variety of a language or dialect.
- 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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 6:08 a.m.