Triple
T323990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chairman of the Central Military Commission |
E6472
|
entity |
| Predicate | currentHolderStartTime |
P7037
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [Chairman of the Central Military Commission, currentHolderStartTime, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentHolderStartTime Context triple: [Chairman of the Central Military Commission, currentHolderStartTime, 2012]
-
A.
currentHolderStart
chosen
Indicates the point in time when an entity’s current holder or possessor first began holding it.
-
B.
lastHolder
Indicates that the subject is the most recent entity to have possessed, owned, or held the object.
-
C.
recordHeldFrom
Indicates that a record or position was held by an entity starting from a specified point in time.
-
D.
isUsuallyHeldBy
Indicates that something is most commonly or typically possessed, carried, or controlled by a particular entity.
-
E.
positionHeld
Indicates that an entity occupies or has occupied a specific role, job, office, or position within an organization or context.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb1a37c08190b1380f6bf8513a37 |
completed | Feb. 28, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69a2e949364c8190bc2351f5413f5057 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.