Triple
T27766696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hànshū |
E701618
|
entity |
| Predicate | excludesDynasty |
P167333
|
FINISHED |
| Object | Eastern Han 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: Eastern Han dynasty | Statement: [Hànshū, excludesDynasty, Eastern Han dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excludesDynasty Context triple: [Hànshū, excludesDynasty, Eastern Han dynasty]
-
A.
extinctDynasty
Indicates that a dynasty has ceased to exist and no longer continues through ruling descendants or recognized lineage.
-
B.
existedUnderDynasty
Indicates that an entity existed or was in effect during the period of a specified dynasty’s rule.
-
C.
nativeDynasty
Indicates that a dynasty is indigenous to, or originally from, the place or polity it rules or is associated with.
-
D.
basedOnDynasty
Indicates that something is derived from, influenced by, or established on the foundation of a particular dynasty.
-
E.
formedDynasty
Indicates that an entity established or created a ruling dynasty.
- F. None of above. chosen
Provenance (4 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 27, 2026, 4:31 p.m.