Triple
T332002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secretary of War |
E6644
|
entity |
| Predicate | officeAbolished |
P9435
|
FINISHED |
| Object | 1947 |
—
|
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: 1947 | Statement: [Secretary of War, officeAbolished, 1947]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeAbolished Context triple: [Secretary of War, officeAbolished, 1947]
-
A.
officeReconstitutedIn
Indicates that an official position or office was re-established or newly formed within a specified location or jurisdiction.
-
B.
combinedOfficeExistedUntil
Indicates that a merged or joint office or position remained in existence up to a specified end time or date.
-
C.
office
Indicates that an entity holds or occupies an official position, role, or post within an organization or institution.
-
D.
abolishedConcept
chosen
Indicates that one entity has formally ended, eliminated, or done away with the other entity as a concept, practice, or institution.
-
E.
officeRestoredIn
Indicates that an office or official position was reinstated or brought back into effect at a particular time or in a specific context.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eab1a7048190ac690ddc2e294914 |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94c6d8881908239d3788c018adf |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.