Triple
T18567819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 軍教育総監 |
E453799
|
entity |
| Predicate | 階級要件 |
P25564
|
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.
nobleRankRequired
Indicates that a certain minimum noble rank or title is required for the related action, status, or relationship to apply.
-
B.
requiresSubjectsAtLevel
Indicates that an entity depends on other subjects being present or qualified at a specified level in order for a condition, action, or state to be valid or achievable.
-
C.
requiresSkillLevel
Indicates that performing or engaging in something depends on possessing at least a specified level of skill.
-
D.
rankRestriction
chosen
Indicates a constraint or limit placed on the rank or hierarchical level that an entity may hold within a given system or structure.
-
E.
boardingRequirement
Indicates the conditions or criteria that must be met for an entity to be allowed to board another entity (such as a vehicle, vessel, or aircraft).
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53affc3e08190b4d16b5ccb0bddbc |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.