Triple
T7308981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tibeto-Burman peoples |
E168043
|
entity |
| Predicate | isDiverseIn |
P64047
|
FINISHED |
| Object | languages |
—
|
LITERAL FINISHED |
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: languages | Statement: [Tibeto-Burman peoples, isDiverseIn, languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDiverseIn Context triple: [Tibeto-Burman peoples, isDiverseIn, languages]
-
A.
hasInternalDiversity
chosen
Indicates that an entity contains multiple distinct types, elements, or subgroups within itself, rather than being uniform or homogeneous.
-
B.
isMostDiverseClassOf
Indicates that one class has the greatest diversity (e.g., in members, attributes, or types) compared to all other classes in a given set.
-
C.
diversifiedIn
Indicates that an entity has expanded its involvement, investments, or activities across multiple different areas, sectors, or asset types.
-
D.
diversity
Indicates the degree to which a set of entities differs along one or more dimensions such as type, attributes, or characteristics.
-
E.
supportsDiversity
Indicates that one entity actively promotes, encourages, or upholds diversity in or for 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_69c6888d8e3c81909db79714903baf31 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebda7b748190a230a22ecea79342 |
completed | March 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:01 p.m.