Triple
T26284410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madam Prime Minister |
E661089
|
entity |
| Predicate | refersToSystem |
P44268
|
FINISHED |
| Object | parliamentary democracy |
—
|
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: parliamentary democracy | Statement: [Madam Prime Minister, refersToSystem, parliamentary democracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToSystem Context triple: [Madam Prime Minister, refersToSystem, parliamentary democracy]
-
A.
isReferenceSystemFor
Indicates that one system serves as the coordinate or measurement framework used to define, locate, or describe positions or values in another system.
-
B.
associatedSystem
Indicates that one entity is functionally or contextually linked to a particular system with which it interacts or to which it belongs.
-
C.
usedBySystem
Indicates that something is utilized or operated by a particular system.
-
D.
refersSpecificallyTo
chosen
Indicates that one entity makes an explicit, precise reference to another particular entity, distinguishing it from more general or ambiguous references.
-
E.
usesSameSystemAs
Indicates that two entities operate within or rely on the same underlying system, platform, or infrastructure.
- 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_69ee812bbd448190be4d7478b057990a |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 26, 2026, 10:03 p.m.