Triple
T24432015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reaper War |
E616021
|
entity |
| Predicate | goalOfReapers |
P156115
|
FINISHED |
| Object | harvesting advanced organic life |
—
|
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: harvesting advanced organic life | Statement: [Reaper War, goalOfReapers, harvesting advanced organic life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalOfReapers Context triple: [Reaper War, goalOfReapers, harvesting advanced organic life]
-
A.
goalOfRebelSide
Indicates that the specified goal is pursued or held by the rebel side in a conflict or opposition scenario.
-
B.
objectiveOfDefenders
Indicates that a particular goal, task, or purpose is assigned to or pursued by the defenders in a given context.
-
C.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
D.
revivalPurpose
Indicates that an action or event is carried out with the aim of bringing something back into use, existence, or prominence.
-
E.
aimsToEliminate
Indicates an intention or directed effort by one entity to remove, destroy, or completely get rid of another entity or condition.
- 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_69e2d7ec44b081909ccaf1f3bbec0641 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29783b3208190997c47be1aa229af |
completed | April 29, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:16 a.m.