Triple
T397017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puebla |
E9204
|
entity |
| Predicate | battleOutcome |
P1421
|
FINISHED |
| Object | Mexican victory over French forces |
—
|
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: Mexican victory over French forces | Statement: [Puebla, battleOutcome, Mexican victory over French forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleOutcome Context triple: [Puebla, battleOutcome, Mexican victory over French forces]
-
A.
gameOutcome
Indicates the result or final status of a game, such as which side won, lost, or if it ended in a draw.
-
B.
typeOfVictory
Indicates the specific manner or category in which a victory was achieved.
-
C.
victoryIn
Indicates that one entity achieves a win or success in a specific contest, event, or competitive context involving another entity.
-
D.
historicalOutcome
chosen
Indicates the result or consequence that an event, action, or situation produced in a historical context.
-
E.
battledIn
Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ec8a941081909a152fda0ce24a98 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96d17d08190878d3a68b17d51ca |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.