Triple
T18328883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KPJ |
E439081
|
entity |
| Predicate | inPowerSystem |
P13999
|
FINISHED |
| Object | one-party system |
—
|
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: one-party system | Statement: [KPJ, inPowerSystem, one-party system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inPowerSystem Context triple: [KPJ, inPowerSystem, one-party system]
-
A.
inPower
chosen
Indicates that one entity currently holds governing authority, control, or leadership over a group, organization, or domain.
-
B.
electricalPower
Indicates that one entity supplies, carries, or is associated with electrical power to or for another entity.
-
C.
inPowerDuring
Indicates that an entity holds a position of authority or governance throughout a specified time period.
-
D.
powering
Indicates that one entity supplies energy or power that enables another entity to operate or function.
-
E.
powerConversionSystem
Indicates a system that transforms electrical power from one form, level, or source into another to meet specific usage or distribution requirements.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aaceb4c81909c4a6b2790602d2e |
completed | April 19, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.