Triple
T12737537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glorious First of June |
E304401
|
entity |
| Predicate | FrenchShipsOfTheLineEngaged |
P106639
|
FINISHED |
| Object | 26 |
—
|
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: 26 | Statement: [Glorious First of June, FrenchShipsOfTheLineEngaged, 26]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FrenchShipsOfTheLineEngaged Context triple: [Glorious First of June, FrenchShipsOfTheLineEngaged, 26]
-
A.
FrenchShips
Indicates that the ships involved are associated with France, typically by nationality, registration, or operation under the French flag.
-
B.
BritishShipsOfTheLine
Indicates a relationship where the subject is classified as a ship of the line that belonged to or was operated by Britain.
-
C.
battleDate(Barfleur)
Indicates the date on which the Battle of Barfleur took place.
-
D.
navalForceInvolved
Indicates that a naval military force participates in, contributes to, or is otherwise involved in a specified event or operation.
-
E.
frigateClassOperated
Indicates that a particular frigate class is operated or used by a given operator (such as a navy, organization, or country).
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d87078c819083ea724238992204 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:26 p.m.