Triple
T29583964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mirifle |
E753670
|
entity |
| Predicate | languageSubfamilyOfDialectSpoken |
P31853
|
FINISHED |
| Object | Cushitic 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: Cushitic languages | Statement: [Mirifle, languageSubfamilyOfDialectSpoken, Cushitic languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageSubfamilyOfDialectSpoken Context triple: [Mirifle, languageSubfamilyOfDialectSpoken, Cushitic languages]
-
A.
usesLanguageSubfamily
Indicates that one entity communicates or operates using a language that belongs to a specified language subfamily.
-
B.
dialectFamily
Indicates that one dialect belongs to, or is classified under, a particular dialect family.
-
C.
languageFamilyOf
Indicates that one entity is the language family to which the other entity (a specific language) belongs.
-
D.
languageGroupSpoken
Indicates that a particular language group is spoken or used for communication by an entity.
-
E.
linguisticSubgroup
chosen
Indicates that one linguistic group forms a subordinate or specialized subset within a larger linguistic group or family.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69feaa483fcc81909d8a46b38a8717bf |
completed | May 9, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69fea8c9d45c81908ccc8619e5fefac1 |
completed | May 9, 2026, 3:23 a.m. |
Created at: April 28, 2026, 6:09 p.m.