Triple
T22050175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tangut |
E544861
|
entity |
| Predicate | hasWritingCorpus |
P65791
|
FINISHED |
| Object | Buddhist texts |
—
|
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: Buddhist texts | Statement: [Tangut, hasWritingCorpus, Buddhist texts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWritingCorpus Context triple: [Tangut, hasWritingCorpus, Buddhist texts]
-
A.
hasNotableCorpus
chosen
Indicates that an entity possesses a significant, well-recognized body of work, texts, or collected materials associated with it.
-
B.
hasPartOfCorpus
Indicates that one entity constitutes a component or segment of the overall corpus associated with another entity.
-
C.
hasWrittenFor
Indicates that one entity has created written content (such as articles, stories, or texts) for or on behalf of another entity, typically a publication, organization, or platform.
-
D.
corpus
Indicates that an entity is a collection or body of texts, documents, or linguistic data used as a unified set for analysis or reference.
-
E.
hasWrittenAbout
Indicates that one entity has authored content or material discussing, analyzing, or referencing 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128323fb08190b9592fd08a96cba0 |
completed | April 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:26 p.m.