Triple
T37133969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thagichu languages |
E919603
|
entity |
| Predicate | haveCommonOriginWith |
P18399
|
FINISHED |
| Object | Kikuyu language |
—
|
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: Kikuyu language | Statement: [Thagichu languages, haveCommonOriginWith, Kikuyu language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveCommonOriginWith Context triple: [Thagichu languages, haveCommonOriginWith, Kikuyu language]
-
A.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
B.
hasCommonReference
Indicates that two or more entities share the same source, citation, or referential basis.
-
C.
hasCommonOriginHypothesis
Indicates that there exists a hypothesis proposing a shared or common origin between the related entities.
-
D.
sharesCommonAncestorWith
chosen
Indicates that two entities have at least one ancestor in common in their lineage or hierarchy.
-
E.
hasCommonElement
Indicates that two sets, collections, or groups share at least one element in common.
- 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.