Triple
T6548387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aluku language |
E151066
|
entity |
| Predicate | hasGlottologStatus |
P28208
|
FINISHED |
| Object | often grouped under Ndyuka |
—
|
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: often grouped under Ndyuka | Statement: [Aluku language, hasGlottologStatus, often grouped under Ndyuka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGlottologStatus Context triple: [Aluku language, hasGlottologStatus, often grouped under Ndyuka]
-
A.
glottologStatus
chosen
Indicates the classification or status of a language or dialect as defined in the Glottolog database.
-
B.
hasGlottologName
Indicates that an entity is associated with a specific name as recorded in the Glottolog linguistic database.
-
C.
glottocode
Indicates the standardized Glottolog code that uniquely identifies the language or dialect associated with an entity.
-
D.
hasEthnologueEntry
Indicates that there exists an entry for the subject in the Ethnologue language reference resource.
-
E.
ISO639_3Status
Indicates the classification or status assigned to a language according to the ISO 639-3 standard (e.g., active, extinct, historical, constructed).
- 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_69c687f3fd60819083bfa583e5bcfa71 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce07332481909a5a7964282eb776 |
completed | March 27, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69c6acf3e3708190b052ec774e607cb7 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:51 p.m.