Triple

T9364858
Position Surface form Disambiguated ID Type / Status
Subject Paestum E225373 entity
Predicate romanName P6662 FINISHED
Object Paestum E225373 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: Paestum | Statement: [Paestum, romanName, Paestum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Paestum
Context triple: [Paestum, romanName, Paestum]
  • A. Paestum chosen
    Paestum is an ancient Greek and later Roman city in southern Italy renowned for its exceptionally well-preserved Doric Greek temples and archaeological remains.
  • B. Metapontum
    Metapontum was an important ancient Greek city in southern Italy, known for its fertile land, temples, and role within the colonies of Magna Graecia.
  • C. Tarquinia
    Tarquinia is an ancient Etruscan city in central Italy renowned for its richly painted tombs and significant archaeological remains.
  • D. Baiae
    Baiae was an ancient Roman resort town on the Bay of Naples famed for its luxurious villas, thermal baths, and popularity among the Roman elite.
  • E. Ligor
    Ligor was an important historical port city and regional center on the Malay Peninsula, known for its role in maritime trade and as a strategic outpost in Southeast Asian empires.
  • 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_69ca842cbddc819099d71ecec48cf9e5 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd503fd7f081909655e2a880c84834 completed April 1, 2026, 5:05 p.m.
NED1 Entity disambiguation (via context triple) batch_69d11019134481908751bed86ff3cac3 completed April 4, 2026, 1:20 p.m.
Created at: March 30, 2026, 7:43 p.m.