Triple
T23916018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dani languages |
E602082
|
entity |
| Predicate | hasISO639_3CodeForMember |
P8719
|
FINISHED |
| Object | dnw (Western Dani) |
—
|
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: dnw (Western Dani) | Statement: [Dani languages, hasISO639_3CodeForMember, dnw (Western Dani)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasISO639_3CodeForMember Context triple: [Dani languages, hasISO639_3CodeForMember, dnw (Western Dani)]
-
A.
hasISO6393Code
chosen
Indicates that a language or linguistic entity is associated with a specific ISO 639-3 three-letter language code.
-
B.
haveISO639Code
Indicates that a language or linguistic entity is associated with a specific ISO 639 standardized language code.
-
C.
hasISO3166Alpha3Code
Indicates that an entity is associated with a specific three-letter country code defined by the ISO 3166-1 alpha-3 standard.
-
D.
hasISO639MacrolanguageCode
Indicates that a language entity is associated with a specific ISO 639 macrolanguage code that represents a broader language grouping.
-
E.
hasMemberLanguage
Indicates that one entity is a language that is a constituent or member of a larger language group, family, or collection 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_69e2953a187081908346a9f36e85fc98 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1ce9917808190ad66a4e276a24b3d |
completed | April 29, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:40 p.m.