Triple
T27848741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weiming clan |
E703893
|
entity |
| Predicate | scriptAssociated |
P16423
|
FINISHED |
| Object | Tangut script |
—
|
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: Tangut script | Statement: [Weiming clan, scriptAssociated, Tangut script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptAssociated Context triple: [Weiming clan, scriptAssociated, Tangut script]
-
A.
relatedToScript
chosen
Indicates a general association or connection between an entity and a script, without specifying the exact nature of that relationship.
-
B.
scriptSource
Indicates that one entity is the origin or provider of the script used or referenced by another entity.
-
C.
scriptType
Indicates the classification or category of a script, specifying what kind of script it is (e.g., its format, purpose, or scripting language type).
-
D.
scriptAncestor
Indicates that one script is an ancestor of another in a script family or derivation hierarchy, meaning the latter historically descends from or is derived from the former.
-
E.
scriptSupport
Indicates that one entity provides or enables scripting capabilities or support 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 27, 2026, 6:09 p.m.