Triple
T18103414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scipion |
E433284
|
entity |
| Predicate | roleInBattleOfNavarino |
P130445
|
FINISHED |
| Object | Allied ship |
—
|
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: Allied ship | Statement: [Scipion, roleInBattleOfNavarino, Allied ship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBattleOfNavarino Context triple: [Scipion, roleInBattleOfNavarino, Allied ship]
-
A.
roleAtBattleOfIquique
Indicates the specific role or function an entity held during the Battle of Iquique.
-
B.
roleInBattleOfTheChesapeake
Indicates the specific function, position, or involvement an entity had in the Battle of the Chesapeake.
-
C.
roleInBattleOfSalamis
Indicates the specific role or involvement an entity had in the Battle of Salamis.
-
D.
navalOpposition
Indicates a relationship where one party actively resists, confronts, or acts against another using naval or maritime military forces.
-
E.
opponentInBattleOfTheRiverPlate
Indicates that two entities were opposing sides facing each other in the Battle of the River Plate.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddb7be948190b4ed4586f731d6f2 |
completed | April 19, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:28 a.m.