Triple
T11698956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Mathews |
E278069
|
entity |
| Predicate | roleAtBattleOfToulon |
P101323
|
FINISHED |
| Object | commander of British fleet |
—
|
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: commander of British fleet | Statement: [Thomas Mathews, roleAtBattleOfToulon, commander of British fleet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtBattleOfToulon Context triple: [Thomas Mathews, roleAtBattleOfToulon, commander of British fleet]
-
A.
roleAtDieppe
Indicates the specific role, position, or function an entity held in connection with the event or context referred to as Dieppe.
-
B.
roleAtTrafalgar
Indicates the specific role, position, or function an entity held during the Battle of Trafalgar.
-
C.
roleAtLeyteGulf
Indicates the specific role or function an entity performed in the context of the Battle of Leyte Gulf.
-
D.
roleAtWaterloo
Indicates the specific position, function, or capacity an entity held in relation to the Battle of Waterloo.
-
E.
opponentInBattleOfCherbourg
Indicates that two entities were opposing sides against each other in the Battle of Cherbourg.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a47df68c81908a91919a69b4880d |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d89546a8688190b51455b5e12caf91 |
completed | April 10, 2026, 6:14 a.m. |
Created at: April 8, 2026, 9:40 p.m.