Triple
T10490354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daju languages |
E247399
|
entity |
| Predicate | haveISO639-5Code |
P19023
|
FINISHED |
| Object | daj |
—
|
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: daj | Statement: [Daju languages, haveISO639-5Code, daj]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveISO639-5Code Context triple: [Daju languages, haveISO639-5Code, daj]
-
A.
hasISO639_5Code
chosen
Indicates that a language or language group is associated with a specific ISO 639-5 code that identifies it within the ISO 639-5 language classification standard.
-
B.
sharesISO639-3CodeWith
Indicates that two language entities share the same ISO 639-3 code, meaning they are treated as the same language in that coding system.
-
C.
hasISO6393Code
Indicates that a language or linguistic entity is associated with a specific ISO 639-3 three-letter language code.
-
D.
ISO639-6Code
Indicates the standardized ISO 639-6 four-letter code that uniquely identifies a specific language variety or dialect.
-
E.
ISO639-3CodeOfLanguage
Indicates that one entity is the ISO 639-3 three-letter language code assigned to the language represented by the other 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5097d61e08190952d4354ef1bce52 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8a30848190b33cf43f005a028e |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:23 p.m.