Triple
T1848005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oromo |
E41327
|
entity |
| Predicate | hasMacrolanguageStatus |
P5218
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Oromo, hasMacrolanguageStatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMacrolanguageStatus Context triple: [Oromo, hasMacrolanguageStatus, true]
-
A.
hasLanguageStatus
Indicates that an entity has a particular status or condition regarding its language use, recognition, or classification.
-
B.
macrolanguageOf
Indicates that one language functions as a macrolanguage encompassing or grouping together one or more related individual languages.
-
C.
macrolanguageMemberOf
Indicates that a language variety is classified as a member of a larger macrolanguage grouping.
-
D.
ISO639Macrolanguage
Indicates that a language variety is part of a broader ISO 639-defined macrolanguage grouping that encompasses multiple closely related individual languages.
-
E.
macrolanguage
chosen
Indicates that a language is classified as a macrolanguage encompassing multiple closely related individual languages or varieties.
- 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdca6d8819083c66f3a29fd9fd1 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.