Triple
T17798689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Military Academy |
E444361
|
entity |
| Predicate | militaryProgramIntroduced |
P128959
|
FINISHED |
| Object | 1896 |
—
|
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: 1896 | Statement: [Western Military Academy, militaryProgramIntroduced, 1896]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryProgramIntroduced Context triple: [Western Military Academy, militaryProgramIntroduced, 1896]
-
A.
introducedMilitaryInstitution
Indicates that an entity established or brought into existence a military institution or organization.
-
B.
introducedWeaponSystem
Indicates that an entity caused a new weapon system to be brought into use or formally adopted.
-
C.
militarySystem
Indicates a relationship where an entity functions as, belongs to, or is characterized by a particular military organizational or operational system.
-
D.
militaryProject
Indicates a project that is conducted, funded, or controlled by a military organization, typically for defense, security, or warfare-related purposes.
-
E.
hasMissileProgramRole
Indicates that an entity holds a specific role, function, or responsibility within a missile program.
- F. None of above. chosen
Provenance (4 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e487fcfdc8819086f41152860dfe18 |
completed | April 19, 2026, 7:45 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:13 a.m.