Triple
T28543448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sima Shi |
E722362
|
entity |
| Predicate | predecessorInRegency |
P180141
|
FINISHED |
| Object | Sima Yi |
—
|
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: Sima Yi | Statement: [Sima Shi, predecessorInRegency, Sima Yi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorInRegency Context triple: [Sima Shi, predecessorInRegency, Sima Yi]
-
A.
predecessorAsHeir
Indicates that one entity previously held the status of heir before being succeeded by another in that role.
-
B.
predecessorAsLocalRuler
Indicates that one entity previously held the position of local ruler immediately before another entity in a given domain or territory.
-
C.
predecessorAsHeirApparent
Indicates that one entity previously held the position of heir apparent to another entity (such as a throne, title, or office) before being succeeded in that role.
-
D.
predecessorAsPrince
Indicates that one entity previously held the title or role of prince before another entity assumed it.
-
E.
predecessorAsCoRuler
Indicates that one entity previously shared ruling authority with another entity before being succeeded in that co-ruler position.
- 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
| PDg | Predicate description generation | batch_69f73221eef88190bd8905e6e9f5a586 |
completed | May 3, 2026, 11:31 a.m. |
Created at: April 28, 2026, 3:37 a.m.