Triple
T17630822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xianbei language |
E429970
|
entity |
| Predicate | possiblyClassifiedAs |
P14654
|
FINISHED |
| Object | Para-Mongolic language |
—
|
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: Para-Mongolic language | Statement: [Xianbei language, possiblyClassifiedAs, Para-Mongolic language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possiblyClassifiedAs Context triple: [Xianbei language, possiblyClassifiedAs, Para-Mongolic language]
-
A.
usuallyClassifiedAs
Indicates that an entity is most commonly or typically placed into a particular category or type, though other classifications may also exist.
-
B.
notClassifiedAs
Indicates that an entity is explicitly not assigned to, or excluded from, a particular class or category.
-
C.
isSometimesClassifiedAs
chosen
Indicates that an entity is occasionally, but not consistently or universally, categorized under a particular type or class.
-
D.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
E.
isClassifiedUnder
Indicates that one entity is categorized or grouped within a broader class, type, or category represented by 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46dc01b1c819099e3329cfb8cb77f |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:52 a.m.