Triple
T14326654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 枝野幸男 |
E355231
|
entity |
| Predicate | 著名な出来事への関与 |
P17461
|
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.
significantEventInvolves
Indicates that a significant event includes or engages a particular entity as a participant or key element.
-
B.
significantEventRole
chosen
Indicates that an entity plays an important or defining role in a particular significant event.
-
C.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
D.
notableUseEvent
Indicates an event in which something is used in a way that is significant or noteworthy, distinguishing it from ordinary or routine use.
-
E.
notableEventMentionedIn
Indicates that a particular notable event is referenced or discussed within a specified source or document.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de883e6a288190b6c22f630a1eef3c |
completed | April 14, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:13 a.m.