Triple
T14930000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivan Alekseyevich |
E372234
|
entity |
| Predicate | heldActualPower |
P33745
|
FINISHED |
| Object | limited |
—
|
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: limited | Statement: [Ivan Alekseyevich, heldActualPower, limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldActualPower Context triple: [Ivan Alekseyevich, heldActualPower, limited]
-
A.
laterPowerOutput
Indicates that the power output of an entity at a later time is being related or compared to its power output at an earlier time.
-
B.
realPower
chosen
Indicates that an entity possesses genuine, effective control or influence over another entity or situation, beyond nominal or formal authority.
-
C.
intendedPower
Indicates the level or amount of power that an entity is designed, planned, or expected to produce, use, or deliver under intended operating conditions.
-
D.
engagedWithPower
Indicates a relationship where an entity actively interacts, collaborates, or aligns with a source of authority, influence, or control.
-
E.
inPowerDuring
Indicates that an entity holds a position of authority or governance throughout a specified time period.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded64550dc8190ba44120df00ba498 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:36 a.m.