Triple
T10489468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Masalit people |
E247375
|
entity |
| Predicate | hasExonymLanguage |
P4705
|
FINISHED |
| Object | Arabic |
—
|
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: Arabic | Statement: [Masalit people, hasExonymLanguage, Arabic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExonymLanguage Context triple: [Masalit people, hasExonymLanguage, Arabic]
-
A.
hasExonym
chosen
Indicates that one entity is known by an alternative name or designation in another language or cultural context.
-
B.
hasEndonymLanguage
Indicates that the language specified is the one in which a name or term is expressed in its own native or local form.
-
C.
hasDemonymLanguage
Indicates that a language is used as the demonym (people’s name or adjective of nationality) for inhabitants of a particular place or group.
-
D.
hasEndonym
Indicates that an entity has a name or designation used by native speakers or within its own local language or community.
-
E.
exonymStatus
Indicates the status or classification of a name used in one language to refer to a place, people, or entity known by a different name in its own language.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5097ca5c081908b47a08ca7885650 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8a30848190b33cf43f005a028e |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:23 p.m.