Triple
T32368397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Wei |
E827060
|
entity |
| Predicate | dynastyUsage |
P126784
|
FINISHED |
| Object | Tang dynasty |
—
|
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: Tang dynasty | Statement: [Prince of Wei, dynastyUsage, Tang dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynastyUsage Context triple: [Prince of Wei, dynastyUsage, Tang dynasty]
-
A.
dynastyProvided
Indicates that a particular dynasty supplied, supported, or was responsible for providing something to another entity or context.
-
B.
dynastyContext
Indicates the historical or cultural dynasty within which an entity, event, or relationship is situated or contextualized.
-
C.
dynasty
Indicates a hereditary ruling line or family that holds power over a state or territory across successive generations.
-
D.
dynasticUse
chosen
Indicates the use of something (such as a name, title, symbol, or resource) in a way that is tied to or characteristic of a particular dynasty or ruling family.
-
E.
dynastyDescribedAs
Indicates that a dynasty is characterized or labeled using a particular description, epithet, or qualitative phrase.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:50 a.m.