Triple
T36670688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dor Bongo |
E905405
|
entity |
| Predicate | hasLinguisticPhylum |
P76549
|
FINISHED |
| Object | Nilo-Saharan |
—
|
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: Nilo-Saharan | Statement: [Dor Bongo, hasLinguisticPhylum, Nilo-Saharan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLinguisticPhylum Context triple: [Dor Bongo, hasLinguisticPhylum, Nilo-Saharan]
-
A.
hasLanguagePhylum
chosen
Indicates that a language belongs to or is classified within a particular language phylum.
-
B.
hasLinguisticStratum
Indicates a relationship where one element is associated with, or belongs to, a particular layer or level within a linguistic structure or system.
-
C.
hasLinguisticDomain
Indicates that something (such as a term, expression, or resource) is associated with or applies within a particular linguistic domain or language context.
-
D.
hasLinguisticTypology
Indicates a relationship where a language or linguistic system is characterized by a specific typological classification or structural type.
-
E.
hasLinguisticHeritage
Indicates that one entity possesses or is associated with the linguistic background, tradition, or ancestry of another entity.
- 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_69f76e6f10008190aea41746aa1b186e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fef3ceef648190b58027c93d757438 |
completed | May 9, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69fef359da2c819091a034387b08821f |
completed | May 9, 2026, 8:42 a.m. |
Created at: May 3, 2026, 4:12 p.m.