Triple
T13891337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Blair ministry |
E333976
|
entity |
| Predicate | legislativeProgram |
P9962
|
FINISHED |
| Object | public service reform |
—
|
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: public service reform | Statement: [Second Blair ministry, legislativeProgram, public service reform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legislativeProgram Context triple: [Second Blair ministry, legislativeProgram, public service reform]
-
A.
legislativeActOf
Indicates a relationship where a legislative act is authored, enacted, or formally issued by a specific legislative body or authority.
-
B.
legislativeActivity
chosen
Indicates involvement in creating, debating, amending, or passing laws or related legislative measures.
-
C.
legislatureComponent
Indicates that one entity is a constituent part or chamber of a larger legislative body.
-
D.
legislativeMechanism
Indicates a relationship where a law, policy, or rule is created, modified, or enacted through a specific formal legislative process or procedure.
-
E.
legislature
Indicates that an entity serves as, or is part of, a law-making body or assembly responsible for creating or amending laws for a political unit.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a537d4819093c2bae2a244816a |
completed | April 14, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69dd464b1ab48190ae50bfc902bf6ef7 |
completed | April 13, 2026, 7:38 p.m. |
Created at: April 9, 2026, 10:15 p.m.