Triple
T15825723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Cyzicus |
E383735
|
entity |
| Predicate | navalForcesUsed |
P23973
|
FINISHED |
| Object | triremes |
—
|
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: triremes | Statement: [Battle of Cyzicus, navalForcesUsed, triremes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalForcesUsed Context triple: [Battle of Cyzicus, navalForcesUsed, triremes]
-
A.
navalForceInvolved
chosen
Indicates that a naval military force participates in, contributes to, or is otherwise involved in a specified event or operation.
-
B.
navalForceComposition
Indicates the makeup and distribution of different types of naval units or vessels within a particular naval force.
-
C.
countryNavalForce
Indicates that a country possesses, controls, or is associated with a particular naval military force.
-
D.
navalFleet
Indicates a relationship where multiple naval vessels are organized and operate together as a coordinated maritime military force.
-
E.
navalFeatures
Indicates that something possesses characteristics, components, or attributes specifically associated with naval or maritime contexts.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e11e602e5481908baa71c3d9b2008f |
completed | April 16, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.