Triple
T27716377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All-Party Parliamentary Pro-Life Group |
E698828
|
entity |
| Predicate | nonDepartmental |
P4926
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [All-Party Parliamentary Pro-Life Group, nonDepartmental, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonDepartmental Context triple: [All-Party Parliamentary Pro-Life Group, nonDepartmental, true]
-
A.
nonGovernmental
Indicates that an entity, action, or relationship is not associated with, controlled by, or part of a government or governmental body.
-
B.
nonClerical
Indicates that an entity, role, or activity is not related to clerical or administrative work or duties.
-
C.
nonPartisan
Indicates that an entity is not affiliated with, influenced by, or acting on behalf of any political party or partisan interest.
-
D.
nonPostNominal
Indicates that the related element does not appear in a post-nominal position (i.e., it does not follow the noun it modifies or relates to).
-
E.
notTiedToSingleDepartment
chosen
Indicates that the entity is not exclusively associated with or restricted to a single department.
- 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f635d0c55c8190bf92bbbe5d363dd1 |
completed | May 2, 2026, 5:35 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 3:04 p.m.