Triple
T11830329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veracruz–Mexico City route |
E281372
|
entity |
| Predicate | endingPointInCampaign |
P390
|
FINISHED |
| Object | capture of Mexico City in 1847 |
—
|
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 of Mexico City in 1847 | Statement: [Veracruz–Mexico City route, endingPointInCampaign, capture of Mexico City in 1847]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endingPointInCampaign Context triple: [Veracruz–Mexico City route, endingPointInCampaign, capture of Mexico City in 1847]
-
A.
locationOfCampaign
Indicates the place or geographic area where a particular campaign is conducted or based.
-
B.
turningPointIn
Indicates that an event or situation serves as a decisive change or pivotal moment within a larger process, narrative, or development.
-
C.
isStartingPointOf
Indicates that something serves as the initial point or origin from which another thing, process, or path begins.
-
D.
endPoint
chosen
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
-
E.
partOfCampaign
Indicates that an entity participates in, belongs to, or is included within a specific campaign.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a62b75dc8190b27d24e46a262a11 |
completed | April 10, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.