Triple
T11825640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | War Pensions Agency |
E281252
|
entity |
| Predicate | isMilitaryOrganization |
P4889
|
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: [War Pensions Agency, isMilitaryOrganization, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMilitaryOrganization Context triple: [War Pensions Agency, isMilitaryOrganization, false]
-
A.
militaryOrganization
chosen
Indicates that an entity functions as, or is associated with, a structured armed forces or defense-related organization.
-
B.
isUnifiedMilitaryOf
Indicates that an entity serves as the single, consolidated military force representing or defending another entity (such as a state, alliance, or organization).
-
C.
hasMilitaryAssociation
Indicates a relationship in which an entity is connected or affiliated with a military organization, activity, or function.
-
D.
isMilitaryOfficer
Indicates that the subject holds an official position as an officer within a military organization.
-
E.
hasMilitaryType
Indicates that an entity is associated with or classified under a specific military category, role, or type.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5eb299481909de3c0e85628fbe4 |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.