Triple

T13521621
Position Surface form Disambiguated ID Type / Status
Subject Battle of the Eurymedon E322909 entity
Predicate approximateGreekFleetSize P61382 FINISHED
Object about 200 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: about 200 triremes | Statement: [Battle of the Eurymedon, approximateGreekFleetSize, about 200 triremes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: approximateGreekFleetSize
Context triple: [Battle of the Eurymedon, approximateGreekFleetSize, about 200 triremes]
  • A. attackingForceApprox chosen
    Indicates that one entity is the approximate attacking force, in terms of size or strength, relative to another entity or context.
  • B. roleInBattleOfSalamis
    Indicates the specific role or involvement an entity had in the Battle of Salamis.
  • C. approximateGallicStrength
    Indicates an estimation or rough calculation of the level or magnitude of Gallic strength in a given context.
  • D. estimatedCarthaginianForces
    Indicates an assessment or approximation of the size or strength of the military forces associated with Carthage.
  • E. hasApproximateDefendingForceSize
    Indicates that an entity is associated with a defending force whose size is known only approximately rather than as an exact value.
  • 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_69d80766a21881909f21a1b7421d3b8a completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbafa3df0c8190804174695587f0ea completed April 12, 2026, 2:43 p.m.
PD Predicate disambiguation batch_69dbae0b63748190b5e207f84b2532ea completed April 12, 2026, 2:36 p.m.
Created at: April 9, 2026, 9:44 p.m.