Triple
T13897253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Maroon War |
E334119
|
entity |
| Predicate | aimOfMaroons |
P46159
|
FINISHED |
| Object | secure autonomy |
—
|
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: secure autonomy | Statement: [First Maroon War, aimOfMaroons, secure autonomy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimOfMaroons Context triple: [First Maroon War, aimOfMaroons, secure autonomy]
-
A.
goalOfRebelSide
chosen
Indicates that the specified goal is pursued or held by the rebel side in a conflict or opposition scenario.
-
B.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
C.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
D.
motiveForUprising
Indicates that a particular factor, condition, or event serves as a motivating cause or justification for an uprising or rebellion.
-
E.
primaryObjectiveConfederate
Indicates that the confederate’s main goal, purpose, or target within a given context is the specified objective.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de25d72c6c819093bf9c43136839d4 |
completed | April 14, 2026, 11:32 a.m. |
| PD | Predicate disambiguation | batch_69dd464b1ab48190ae50bfc902bf6ef7 |
completed | April 13, 2026, 7:38 p.m. |
Created at: April 9, 2026, 10:15 p.m.