Triple
T21257241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Cerro de Pasco |
E523899
|
entity |
| Predicate | controlledAfterBattle |
P21851
|
FINISHED |
| Object | Cerro de Pasco under patriot influence |
—
|
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: Cerro de Pasco under patriot influence | Statement: [Battle of Cerro de Pasco, controlledAfterBattle, Cerro de Pasco under patriot influence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledAfterBattle Context triple: [Battle of Cerro de Pasco, controlledAfterBattle, Cerro de Pasco under patriot influence]
-
A.
controlledAfter
chosen
Indicates that one entity gains or maintains control over another entity only after a specified time, event, or condition has occurred.
-
B.
statusAfterBattle
Indicates the condition or state of an entity following the completion of a battle or combat encounter.
-
C.
missionPhaseAfter
Indicates that one mission phase occurs later in sequence or time than another mission phase.
-
D.
controlDuringBattle
Indicates that one entity exerts command, influence, or strategic direction over another specifically in the context of a battle or combat situation.
-
E.
statusAfterMission
Indicates the condition or state an entity is in following the completion of a mission.
- 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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735e2f1d48190b566ab4d736fdbc4 |
completed | April 21, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:58 p.m.