Triple
T21461835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 陸軍次官 |
E529489
|
entity |
| Predicate | 歴史的分類 |
P9609
|
FINISHED |
| Object | 旧軍官僚制度の一部 |
—
|
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: 旧軍官僚制度の一部 | Statement: [陸軍次官, 歴史的分類, 旧軍官僚制度の一部]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 歴史的分類 Context triple: [陸軍次官, 歴史的分類, 旧軍官僚制度の一部]
-
A.
historicalClassificationEnd
Indicates the point in time when a particular historical classification or categorization of an entity ceases to be valid.
-
B.
historicalClassificationStart
Indicates the point in time when a particular historical classification or categorization of an entity begins to apply.
-
C.
historicalType
Indicates that one entity classifies or characterizes another in terms of its role, status, or category within a historical context.
-
D.
historicalCategory
chosen
Indicates that an entity is classified within a particular historical grouping, period, or type based on its time-related characteristics or context.
-
E.
chronologicallyClassifiedAs
Indicates that something is assigned to or placed within a specific time period or chronological category.
- 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9ef0c0881908554977df00604a6 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:09 p.m.