Triple
T11418334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anne Hilarion de Costentin de Tourville |
E270550
|
entity |
| Predicate | battleDate(BeachyHead) |
P80256
|
FINISHED |
| Object | 1690-07-10 |
—
|
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: 1690-07-10 | Statement: [Anne Hilarion de Costentin de Tourville, battleDate(BeachyHead), 1690-07-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleDate(BeachyHead) Context triple: [Anne Hilarion de Costentin de Tourville, battleDate(BeachyHead), 1690-07-10]
-
A.
battleOccurredOn
Indicates that a specific battle took place at or on a particular location or date.
-
B.
battleOfJutlandDate
chosen
Indicates the specific calendar date on which the Battle of Jutland took place.
-
C.
battleOccurredNear
Indicates that a battle took place in spatial proximity to a specified location or entity.
-
D.
enemyEngagementAtJutland
Indicates that an entity participated in or was involved in hostile military action against an enemy during the Battle of Jutland.
-
E.
placeOfMainEngagement
Indicates the primary location where an entity carries out its main activities, operations, or engagements.
- 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_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. |
Created at: April 8, 2026, 9:34 p.m.