Triple
T25774687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Formigny |
E649114
|
entity |
| Predicate | battlePhaseOf |
P72305
|
FINISHED |
| Object | closing phase of the Hundred Years’ War |
—
|
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: closing phase of the Hundred Years’ War | Statement: [Formigny, battlePhaseOf, closing phase of the Hundred Years’ War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battlePhaseOf Context triple: [Formigny, battlePhaseOf, closing phase of the Hundred Years’ War]
-
A.
warPhase
chosen
Indicates the specific stage or period within a war or armed conflict during which an event, action, or condition occurs.
-
B.
bossBattlePhase
Indicates the specific stage or phase within a boss battle that an entity is currently engaged in.
-
C.
battleSystem
Indicates a relationship where entities are engaged in or governed by a structured combat or conflict-resolution mechanism.
-
D.
commonRacePhase
Indicates that two or more race events share the same phase or stage within a larger racing sequence or structure.
-
E.
hasPhaseOfPlay
Indicates a relationship where a broader game or activity includes or is associated with a specific phase or segment of play.
- 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fe5be4a8819083e43efecd8423a0 |
completed | May 2, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 5:33 a.m.