Triple
T15536185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mega-Kaiju in Tokyo |
E370351
|
entity |
| Predicate | attackObjective |
P38945
|
FINISHED |
| Object | reach Mount Fuji |
—
|
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: reach Mount Fuji | Statement: [Battle of Mega-Kaiju in Tokyo, attackObjective, reach Mount Fuji]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackObjective Context triple: [Battle of Mega-Kaiju in Tokyo, attackObjective, reach Mount Fuji]
-
A.
objectiveOfAttackers
Indicates the target or goal that attackers aim to reach or affect through their attack.
-
B.
actorObjective
Indicates that an actor has a specific goal, purpose, or intended outcome in relation to another entity or situation.
-
C.
aimOfAttacker
chosen
Indicates that a particular goal, target, or objective is what the attacker intends to achieve or affect.
-
D.
aimsToCapture
Indicates an intention or effort by one entity to take control of, seize, or gain possession of another entity.
-
E.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0442e327c8190b4b879c8a3cd38e3 |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:06 a.m.