Triple
T690346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canarian Spanish |
E13376
|
entity |
| Predicate | ISO639-3Status |
P6525
|
FINISHED |
| Object | not assigned a separate ISO 639-3 code |
—
|
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: not assigned a separate ISO 639-3 code | Statement: [Canarian Spanish, ISO639-3Status, not assigned a separate ISO 639-3 code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISO639-3Status Context triple: [Canarian Spanish, ISO639-3Status, not assigned a separate ISO 639-3 code]
-
A.
ISO639_3Status
chosen
Indicates the classification or status assigned to a language according to the ISO 639-3 standard (e.g., active, extinct, historical, constructed).
-
B.
languageCodeISO639-2
Indicates that an entity is associated with a language identified by its ISO 639-2 three-letter code.
-
C.
hasISO6393Code
Indicates that a language or linguistic entity is associated with a specific ISO 639-3 three-letter language code.
-
D.
glottocode
Indicates the standardized Glottolog code that uniquely identifies the language or dialect associated with an entity.
-
E.
languageEndangermentStatus
Indicates the degree to which a language is at risk of falling out of use or becoming extinct.
- 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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0ad379c81909003d35c63822780 |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d221d38819083c0adda81f59b07 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.