Triple
T15917399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Tirad Pass |
E386003
|
entity |
| Predicate | objectiveAmerican |
P96700
|
FINISHED |
| Object | capture Emilio Aguinaldo |
—
|
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: capture Emilio Aguinaldo | Statement: [Battle of Tirad Pass, objectiveAmerican, capture Emilio Aguinaldo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectiveAmerican Context triple: [Battle of Tirad Pass, objectiveAmerican, capture Emilio Aguinaldo]
-
A.
objectiveOfUnitedStates
Indicates that something is an official objective or goal pursued by the United States.
-
B.
usesObjective
Indicates that an agent employs or applies a particular object, tool, or resource to carry out an action or achieve a goal.
-
C.
objectiveIncludes
Indicates that a broader objective encompasses or contains a specific sub-objective, component, or element as part of its scope.
-
D.
primaryObjectiveOfAmericans
chosen
Indicates that the linked concept represents the main goal, aim, or overarching purpose pursued by Americans.
-
E.
objectiveOfUSForces
Indicates that a specified goal, target, or mission serves as an objective assigned to or pursued by U.S. military forces.
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:52 a.m.