Triple
T22139890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 岡田啓介 |
E547128
|
entity |
| Predicate | 知られている理由 |
P140060
|
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.
knownToBe
chosen
Indicates that one entity is recognized or acknowledged as being a certain way, having a certain property, or fitting a particular description by others.
-
B.
knows
Indicates that one entity has knowledge or awareness of another entity or piece of information.
-
C.
knownForDecision
Indicates that an entity is recognized or notable specifically for making a particular decision.
-
D.
knownFrom
Indicates that one entity is aware of, has learned about, or recognizes another entity through a specified source, context, or medium.
-
E.
visibilityReason
Indicates the reason or cause for why something is visible or has become visible in a given context.
- 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_69e11e3a95d88190a3bd80d9471976c3 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129bda1208190b851ae5c68b760e9 |
completed | April 28, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:32 p.m.