Triple
T36381518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tai Nüa language |
E896057
|
entity |
| Predicate | usesClassifierSystem |
P48601
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tai Nüa language, usesClassifierSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesClassifierSystem Context triple: [Tai Nüa language, usesClassifierSystem, yes]
-
A.
usesClassifiers
chosen
Indicates that one entity employs or relies on a system of classifiers (such as category labels or measure words) when referring to or organizing another entity.
-
B.
usesClassificationCriteria
Indicates that one entity applies specific classification criteria to categorize, organize, or evaluate another entity.
-
C.
classificationSystem
Indicates a relationship where an entity is organized or categorized according to a particular classification scheme or taxonomy.
-
D.
classificationSystemBasedOn
Indicates that one classification system is organized, defined, or derived using another classification system as its basis or reference framework.
-
E.
usedToClassify
Indicates that one entity serves as a criterion or basis for categorizing or grouping 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_69f76e51d358819092bbc5f119f49476 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: May 3, 2026, 4:10 p.m.