Triple
T31461939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Zhi of Han |
E802623
|
entity |
| Predicate | notablePowerHolder |
P66131
|
FINISHED |
| Object | Liang Ji |
E1972045
|
NE 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: Liang Ji | Statement: [Emperor Zhi of Han, notablePowerHolder, Liang Ji]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePowerHolder Context triple: [Emperor Zhi of Han, notablePowerHolder, Liang Ji]
-
A.
deFactoPowerHolder
chosen
Indicates that an entity is the one effectively exercising power or control in practice, regardless of formal or legal authority.
-
B.
notableOfficeHolder
Indicates that an entity is a significant or distinguished holder of a particular office or position associated with another entity.
-
C.
notablePolitician
Indicates that the subject is a politician who is recognized as notable or significant in a political context.
-
D.
notableLeaderSide
Indicates that a person is a prominent or distinguished leader associated with a particular side, faction, or party in a conflict or competition.
-
E.
notableFormerLeader
Indicates that the subject was once a leader of the object and is recognized as particularly significant or prominent in that former leadership role.
- F. None of above.
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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b849b3ed48190a19f2526ac318de7 |
completed | June 12, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 9:20 p.m.