Triple
T8411779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mylae |
E198640
|
entity |
| Predicate | CarthaginianFleetSize |
P31444
|
FINISHED |
| Object | approximately 130 warships |
—
|
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: approximately 130 warships | Statement: [Battle of Mylae, CarthaginianFleetSize, approximately 130 warships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CarthaginianFleetSize Context triple: [Battle of Mylae, CarthaginianFleetSize, approximately 130 warships]
-
A.
estimatedCarthaginianForces
chosen
Indicates an assessment or approximation of the size or strength of the military forces associated with Carthage.
-
B.
CarthaginianCommander
Indicates that the subject serves as a military commander for Carthage or is identified as holding a commanding role within the Carthaginian forces.
-
C.
attackingForceApprox
Indicates that one entity is the approximate attacking force, in terms of size or strength, relative to another entity or context.
-
D.
SpanishFleetStrength
Indicates the relative size or power of a Spanish naval fleet in a given context or time.
-
E.
embarkedForcesCapacity
Indicates the maximum number of forces (e.g., troops or personnel) that can be embarked or carried by a given platform or unit.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb83e0341c819080506e696131671e |
completed | March 31, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69cb70d473dc8190af8ea81ee5aa970d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:05 p.m.