Triple
T11418335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anne Hilarion de Costentin de Tourville |
E270550
|
entity |
| Predicate | battleDate(Barfleur) |
P99199
|
FINISHED |
| Object | 1692-05-29 |
—
|
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: 1692-05-29 | Statement: [Anne Hilarion de Costentin de Tourville, battleDate(Barfleur), 1692-05-29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleDate(Barfleur) Context triple: [Anne Hilarion de Costentin de Tourville, battleDate(Barfleur), 1692-05-29]
-
A.
opponentInBattleOfCherbourg
Indicates that two entities were opposing sides against each other in the Battle of Cherbourg.
-
B.
battleSecuredForNapoleon
Indicates that a battle was won or decisively secured in favor of Napoleon.
-
C.
FrenchShips
Indicates that the ships involved are associated with France, typically by nationality, registration, or operation under the French flag.
-
D.
navalEngagementType
Indicates the specific kind or category of naval combat or maritime military engagement involved in the relationship.
-
E.
battleOccurredOn
Indicates that a specific battle took place at or on a particular location or date.
- F. None of above. chosen
Provenance (4 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d801b0236c81908122ce3fc7b4fde7 |
completed | April 9, 2026, 7:44 p.m. |
| PD | Predicate disambiguation | batch_69d7e70ffd708190b62a78ebcbce9f78 |
completed | April 9, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69d80010712c819089ea2e31e664abe1 |
completed | April 9, 2026, 7:37 p.m. |
Created at: April 8, 2026, 9:34 p.m.