Triple
T25441124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biate |
E637507
|
entity |
| Predicate | hasLanguageFamilyHigher |
P170932
|
FINISHED |
| Object | Sino-Tibetan |
—
|
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: Sino-Tibetan | Statement: [Biate, hasLanguageFamilyHigher, Sino-Tibetan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageFamilyHigher Context triple: [Biate, hasLanguageFamilyHigher, Sino-Tibetan]
-
A.
isInLanguageFamily
Indicates that a language belongs to, or is classified within, a particular language family based on shared linguistic ancestry or characteristics.
-
B.
usesLanguageFamily
Indicates that an entity communicates or operates using a language that belongs to a specified language family.
-
C.
inLanguageFamily
Indicates that two languages belong to the same linguistic family or classification.
-
D.
derivedFromLanguageFamily
Indicates that one language originates from, or historically descends from, a particular language family.
-
E.
hasSuperordinateLanguage
Indicates that one language serves as a higher-level, overarching, or more general language in relation to another language.
- F. None of above. chosen
Provenance (4 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6984bb55c8190862eb8796868d188 |
completed | May 3, 2026, 12:35 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f6978ec27c8190a488e1f9c2566d38 |
completed | May 3, 2026, 12:32 a.m. |
Created at: April 21, 2026, 2 p.m.