Triple
T28096117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shenfeng |
E710095
|
entity |
| Predicate | chronologicalOrderInSunQuanReign |
P174198
|
FINISHED |
| Object | fourth era name |
—
|
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: fourth era name | Statement: [Shenfeng, chronologicalOrderInSunQuanReign, fourth era name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalOrderInSunQuanReign Context triple: [Shenfeng, chronologicalOrderInSunQuanReign, fourth era name]
-
A.
chronologicalOrderInSuccessionWar
Indicates the temporal sequence in which entities participate or occur within the context of the Succession War.
-
B.
eraSequenceInEmperorLingReign
Indicates that one era directly follows another within the chronological sequence of Emperor Ling’s reign.
-
C.
chronologyWithinReignOf
Indicates that one event or time period occurs entirely within the span of a specified ruler’s reign.
-
D.
eraSequenceWithinDynasty
Indicates that one historical era occurs in a specific ordered position relative to another era within the same dynasty.
-
E.
eraSequenceInReign
chosen
Indicates the ordinal position of a specific era within the chronological sequence of eras that occur during a particular ruler’s reign.
- 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_69ef9b70fd108190a875953b2e50ca91 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 27, 2026, 9:01 p.m.