Triple
T16988848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emomali Rahmon |
E412139
|
entity |
| Predicate | previousPositionHeldEnd |
P33300
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [Emomali Rahmon, previousPositionHeldEnd, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousPositionHeldEnd Context triple: [Emomali Rahmon, previousPositionHeldEnd, 1994]
-
A.
positionHeld
Indicates that an entity occupies or has occupied a specific role, job, office, or position within an organization or context.
-
B.
lastHeldIn
Indicates that an event or state most recently took place or was hosted in a particular location or context.
-
C.
heldByEnd
Indicates that an object or item is being held or supported specifically at one of its ends by an agent or another object.
-
D.
termEndOfLastHolder
chosen
Indicates that something marks the end point of the term or tenure of the most recent previous holder of a role, position, or asset.
-
E.
lastHeldBeforeRemoval
Indicates that an entity was the final holder or possessor of another entity immediately prior to that entity’s removal or deletion.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d27dca248190a9b73b16439d5631 |
completed | April 18, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.