Triple
T15386427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaiju War |
E367927
|
entity |
| Predicate | goalOfHumanity |
P118574
|
FINISHED |
| Object | defend Earth from kaiju attacks |
—
|
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: defend Earth from kaiju attacks | Statement: [Kaiju War, goalOfHumanity, defend Earth from kaiju attacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalOfHumanity Context triple: [Kaiju War, goalOfHumanity, defend Earth from kaiju attacks]
-
A.
goalIn
Indicates that one entity’s objective, aim, or intended outcome is located within, directed toward, or achieved inside another entity or context.
-
B.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
C.
goalInDebate
Indicates that one party has a specific objective or desired outcome they are trying to achieve within the context of a debate or argumentative exchange.
-
D.
laterSocietyGoal
Indicates that a society adopts or aims to achieve a particular goal at a later time or stage in its development.
-
E.
goalsFor
Indicates the number of goals scored by one participant or team in favor of a particular side or match context.
- F. None of above. chosen
Provenance (4 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e74ff70819094c1a85f51d6e228 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:19 a.m.