Triple
T90543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secretary of State for War |
E1818
|
entity |
| Predicate | combinedOfficeExistedFrom |
P2719
|
FINISHED |
| Object | 1801 |
—
|
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: 1801 | Statement: [Secretary of State for War, combinedOfficeExistedFrom, 1801]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combinedOfficeExistedFrom Context triple: [Secretary of State for War, combinedOfficeExistedFrom, 1801]
-
A.
establishedOffice
Indicates that an entity created or set up an official office or place of operation.
-
B.
hasOffice
Indicates that an entity possesses or maintains an office at a particular location or within a specific organization.
-
C.
officeInvolved
Indicates that a particular office or organizational unit is involved or participates in a specified event, action, or relationship.
-
D.
successorOfficeTo
Indicates that one office or position directly follows and replaces another in an official sequence or hierarchy.
-
E.
recognizedAsOfficeSince
chosen
Indicates that an entity has been officially designated or acknowledged as an office starting from a specific point in time.
- 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_69a24d1a97dc819094e6c021fe9b05a7 |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a24feef1b08190bb9525f71cce053e |
completed | Feb. 28, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69a24eb82d408190b0f9c786152e8e4c |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:07 a.m.