Triple
T19870991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicobarese |
E477515
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Nancowry language |
—
|
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: Nancowry language | Statement: [Nicobarese, hasPart, Nancowry language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nancowry language Context triple: [Nicobarese, hasPart, Nancowry language]
-
A.
Nancowry language
chosen
Nancowry language is an Austroasiatic language spoken by the Nicobarese people on Nancowry and nearby islands in India’s Nicobar archipelago.
-
B.
Tharawal language
Tharawal language is an Australian Aboriginal language traditionally spoken by the Tharawal people of coastal New South Wales, south of Sydney.
-
C.
Nankani language
The Nankani language is a Gur language spoken primarily by the Nankani people in northern Ghana and parts of Burkina Faso.
-
D.
Belhare language
The Belhare language is a Kiranti language of the Sino-Tibetan family spoken by the Belhare community in eastern Nepal.
-
E.
Tindi language
The Tindi language is a Northeast Caucasian language spoken by the Tindi people in Dagestan, Russia, known for its complex grammar and limited number of speakers.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658a3d2b08190ad81914d4860df0e |
completed | April 20, 2026, 4:47 p.m. |
Created at: April 10, 2026, 1:51 p.m.