Triple
T24139096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proto-Tibeto-Burman |
E598173
|
entity |
| Predicate | isBranchAncestorOf |
P369
|
FINISHED |
| Object | Tibetic 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: Tibetic languages | Statement: [Proto-Tibeto-Burman, isBranchAncestorOf, Tibetic languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBranchAncestorOf Context triple: [Proto-Tibeto-Burman, isBranchAncestorOf, Tibetic languages]
-
A.
isAnabranchOf
Indicates that one watercourse branches off from a main river or stream and later rejoins it, forming a secondary channel of the same system.
-
B.
hasAncestor
chosen
Indicates that one entity is an ancestor (direct or indirect, such as a parent, grandparent, etc.) of another entity in a genealogical or hierarchical lineage.
-
C.
hasAncestralTo
Indicates that one entity is an ancestor of another, existing in an earlier generation within a lineage or heritage chain.
-
D.
destinedAncestorOf
Indicates that one entity is fated or preordained to become an ancestor of another entity in the future.
-
E.
isGrandchildOf
Indicates that one person is the grandchild (child of a child) of another person.
- 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e004fd38819080135a069e98a3e1 |
completed | April 29, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:27 p.m.