Triple
T25099910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Engager War |
E628693
|
entity |
| Predicate | aimOfEngagers |
P64674
|
FINISHED |
| Object | conditional restoration of Charles I |
—
|
NE NERFINISHED |
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: conditional restoration of Charles I | Statement: [Engager War, aimOfEngagers, conditional restoration of Charles I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimOfEngagers Context triple: [Engager War, aimOfEngagers, conditional restoration of Charles I]
-
A.
aimOf
chosen
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
B.
seeksEngagementWith
Indicates an entity’s active effort or intention to initiate or maintain interaction, involvement, or responsive connection with another entity.
-
C.
aimOfAttacker
Indicates that a particular goal, target, or objective is what the attacker intends to achieve or affect.
-
D.
engagementOf
Indicates a relationship where an engagement, commitment, or formal involvement is associated with or attributed to a specific entity.
-
E.
engagementTo
Indicates a formal promise or commitment between two entities to enter into a future partnership or binding relationship.
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f46d3f35848190b56a4373c97a7d64 |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 6:25 a.m.