Triple
T24651809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parliamentary State Secretary |
E610268
|
entity |
| Predicate | isCivilServantPosition |
P62141
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Parliamentary State Secretary, isCivilServantPosition, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCivilServantPosition Context triple: [Parliamentary State Secretary, isCivilServantPosition, false]
-
A.
isCivilianOffice
Indicates that an office or position is non-military and belongs to the civilian sphere of authority or administration.
-
B.
positionOnCivilService
chosen
Indicates the role, rank, or status an individual holds within a civil service system.
-
C.
isNonCabinetPosition
Indicates that the position held by an individual is not part of the official cabinet-level roles within a government or organization.
-
D.
isMinisterialRole
Indicates that a given role is a ministerial position, typically associated with governmental or religious ministry responsibilities.
-
E.
isOfficerOf
Indicates that one entity holds an official position, role, or office within another entity (such as an organization, group, or institution).
- 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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:34 a.m.