Triple
T17320002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 内務大臣 |
E420533
|
entity |
| Predicate | wasKeyPostIn |
P24109
|
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: [内務大臣, wasKeyPostIn, 藩閥政府]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasKeyPostIn Context triple: [内務大臣, wasKeyPostIn, 藩閥政府]
-
A.
isKeyPostIn
chosen
Indicates that a post or position is a central, strategically important element within a specified organization, structure, or context.
-
B.
wasIn
Indicates that an entity existed, occurred, or was located within a particular place or context during a specified time or situation.
-
C.
wasLast
Indicates that one entity occurred or appeared after all others in a sequence, making it the final item or event.
-
D.
wereInternedBy
Indicates that an entity was forcibly confined, detained, or held in an internment facility by another entity (typically an authority or government).
-
E.
wasA
Indicates that an entity previously had a certain role, type, or classification in the past.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439a066b481908e8aee1885809eba |
completed | April 19, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:43 a.m.