Triple
T32688791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tianji |
E835799
|
entity |
| Predicate | usedInDynasticPeriod |
P111642
|
FINISHED |
| Object | Three Kingdoms period |
—
|
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: Three Kingdoms period | Statement: [Tianji, usedInDynasticPeriod, Three Kingdoms period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInDynasticPeriod Context triple: [Tianji, usedInDynasticPeriod, Three Kingdoms period]
-
A.
usedDuringDynasty
chosen
Indicates that something (such as an object, practice, or concept) was in use during the time period of a specific dynasty.
-
B.
dynasticUse
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.
-
C.
existedUnderDynasty
Indicates that an entity existed or was in effect during the period of a specified dynasty’s rule.
-
D.
usedForPartOfReignOf
Indicates that something was employed or in effect during a specific portion of a ruler’s or leader’s time in power.
-
E.
hasDynasticSignificance
Indicates that something holds importance or influence within the context of a dynasty’s continuity, status, or historical legacy.
- 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_69f3493211388190993801216afbc2a7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
Created at: May 1, 2026, 1:09 a.m.