Triple
T33847461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camus language |
E867521
|
entity |
| Predicate | languageCluster |
P134083
|
FINISHED |
| Object | Maa languages |
—
|
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: Maa languages | Statement: [Camus language, languageCluster, Maa languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageCluster Context triple: [Camus language, languageCluster, Maa languages]
-
A.
languageGroupAttribution
chosen
Indicates that an entity is associated with, classified under, or attributed to a particular language group.
-
B.
languageCategory
Indicates the classification relationship where a language is assigned to a particular linguistic or functional category.
-
C.
majorLanguageGroupOf
Indicates that one language group is the primary or dominant linguistic classification to which another language or set of languages belongs.
-
D.
languageGroupSpoken
Indicates that a particular language group is spoken or used for communication by an entity.
-
E.
languageArea
Indicates the geographic or cultural region in which a particular language is used or predominantly spoken.
- 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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a003f6083608190a5deadc7291cf70e |
completed | May 10, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_6a003c935c40819085fdb255a52ba03b |
completed | May 10, 2026, 8:06 a.m. |
Created at: May 1, 2026, 1:47 a.m.