Triple
T111447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mako Mori |
E2255
|
entity |
| Predicate | fightsAgainst |
P4567
|
FINISHED |
| Object | Kaiju |
—
|
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: Kaiju | Statement: [Mako Mori, fightsAgainst, Kaiju]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fightsAgainst Context triple: [Mako Mori, fightsAgainst, Kaiju]
-
A.
opposingForce
chosen
Indicates a relationship where one entity actively resists, counters, or works against the actions, goals, or influence of another entity.
-
B.
primaryEnemy
Indicates that one entity is the main or most significant adversary or opponent of another entity.
-
C.
struggleFor
Indicates a relationship where one entity exerts effort or engages in conflict in order to obtain, achieve, or defend another entity or goal.
-
D.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
E.
mainCombatant
Indicates that the subject is the primary participant or leading party in a conflict, battle, or combat situation involving the object.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a258b58efc8190959c86f73d67b744 |
completed | Feb. 28, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69a25641058c8190b5b64509b35d8176 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.