Triple
T32192114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanamits |
E822283
|
entity |
| Predicate | publicGoalClaimed |
P197828
|
FINISHED |
| Object | to end war on Earth |
—
|
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: to end war on Earth | Statement: [Kanamits, publicGoalClaimed, to end war on Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicGoalClaimed Context triple: [Kanamits, publicGoalClaimed, to end war on Earth]
-
A.
resultClaimed
Indicates that an entity asserts or declares a particular outcome or result as having occurred or being true.
-
B.
claimedFor
Indicates that one entity has asserted ownership, responsibility, or entitlement over or on behalf of another entity.
-
C.
challengesClaim
Indicates that one entity disputes, questions, or opposes the validity or correctness of another entity’s claim.
-
D.
attemptedClaim
Indicates that an entity made an effort to assert or demand a claim, regardless of whether the claim was ultimately accepted or successful.
-
E.
claimPassedTo
Indicates that a claim has been transferred from one party or system to another, typically for further processing, ownership, or responsibility.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
| PDg | Predicate description generation | batch_69feafa0acd881908bb6c01635b5537a |
completed | May 9, 2026, 3:53 a.m. |
Created at: May 1, 2026, 12:35 a.m.