Triple
T1061666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Under Secretary of State for Political Affairs |
E22919
|
entity |
| Predicate | officeLevel |
P14125
|
FINISHED |
| Object | sub-cabinet level position |
—
|
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: sub-cabinet level position | Statement: [Under Secretary of State for Political Affairs, officeLevel, sub-cabinet level position]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeLevel Context triple: [Under Secretary of State for Political Affairs, officeLevel, sub-cabinet level position]
-
A.
designationLevel
chosen
Indicates the specific rank, tier, or level assigned to an entity within a designation or classification system.
-
B.
office
Indicates that an entity holds or occupies an official position, role, or post within an organization or institution.
-
C.
officeInvolved
Indicates that a particular office or organizational unit is involved or participates in a specified event, action, or relationship.
-
D.
leftOffice
Indicates that an entity ceased holding or performing the duties of a particular office or position.
-
E.
officeCategory
Indicates the classification or type of an office within a defined categorization scheme.
- 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4ba6e35ac8190802341c31bda0e3b |
completed | March 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69a4b7340a048190807363f19d17a58f |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.