Triple
T11877872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oro people |
E282577
|
entity |
| Predicate | nativeLanguage |
P151
|
FINISHED |
| Object | Oro language |
E951885
|
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: Oro language | Statement: [Oro people, nativeLanguage, Oro language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oro language Context triple: [Oro people, nativeLanguage, Oro language]
-
A.
Oro language
chosen
The Oro language is the traditional indigenous language spoken by the Oro people of Papua New Guinea.
-
B.
Oron language
The Oron language is a Niger-Congo language spoken by the Oron people of southeastern Nigeria, particularly in coastal areas of Akwa Ibom State.
-
C.
Wayoró language
The Wayoró language is an indigenous Tupian language spoken by the Wayoró people of the Brazilian Amazon.
-
D.
Orok language
The Orok language is a critically endangered Tungusic language spoken by the Orok (Uilta) people of Sakhalin Island in Russia.
-
E.
Arosi language
The Arosi language is an Oceanic language spoken primarily on Makira Island in the Solomon Islands.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8be1b6a5c81909a18c54205dda09c |
completed | April 10, 2026, 9:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f417cb1c3881909ee50e8d11621664 |
completed | May 1, 2026, 3:02 a.m. |
Created at: April 8, 2026, 9:44 p.m.