Triple

T10859599
Position Surface form Disambiguated ID Type / Status
Subject Metauro River E256362 entity
Predicate LatinName P3646 FINISHED
Object Metaurus E888547 NE 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: Metaurus | Statement: [Metauro River, LatinName, Metaurus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Metaurus
Context triple: [Metauro River, LatinName, Metaurus]
  • A. Metaurus chosen
    Metaurus is an ancient name for the Metauro River in Italy, known as the site of a decisive battle in the Second Punic War.
  • B. Latreillius
    Latreillius is a genus of crustaceans named in honor of the French zoologist and entomologist Pierre André Latreille.
  • C. Capurrius
    Capurrius is a Latinized variant of the Italian surname Capurro, likely used in historical or scholarly contexts.
  • D. Arcesius
    Arcesius is a figure in Greek mythology, known as the son of Zeus and the father of Laertes, making him the grandfather of Odysseus.
  • E. Hannibalianus
    Hannibalianus was a 4th-century Roman nobleman and member of Constantine the Great’s family, briefly elevated with a royal title during the emperor’s eastern campaigns before being executed in the dynastic purges of 337.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d6aa83d1448190a66d93c32394d21f completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d75150ceb88190a70356d12ce130c5 completed April 9, 2026, 7:12 a.m.
NED1 Entity disambiguation (via context triple) batch_69dff7d0403c8190bc0b92197a25d3ee completed April 15, 2026, 8:40 p.m.
Created at: April 8, 2026, 9:20 p.m.