Triple
T6728613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vietic languages |
E153577
|
entity |
| Predicate | endangeredMembers |
P73394
|
FINISHED |
| Object | Rục language |
E615583
|
NE 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: Rục language | Statement: [Vietic languages, endangeredMembers, Rục language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rục language Context triple: [Vietic languages, endangeredMembers, Rục language]
-
A.
Rục language
chosen
Rục language is a highly endangered Vietic language spoken by the small Rục ethnic group in the mountainous regions of central Vietnam.
-
B.
Rumsen language
Rumsen language is an extinct Ohlone (Costanoan) Native American language formerly spoken in the Monterey Bay area of California.
-
C.
Rarámuri language
The Rarámuri language is an indigenous Uto-Aztecan language spoken by the Tarahumara (Rarámuri) people of northern Mexico.
-
D.
Munduruku language
The Munduruku language is an indigenous Tupian language spoken by the Munduruku people of the Amazon region in Brazil.
-
E.
Logba language
The Logba language is a Niger-Congo language spoken by the Logba people of southeastern Ghana.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c6880bdd68819097de8b6099992682 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d7c94bac8190ae4b236d1b04bec9 |
completed | March 27, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7129cb39c8190beb02f0d7ea19d8a |
completed | March 27, 2026, 11:28 p.m. |
Created at: March 27, 2026, 2:08 p.m.