Triple

T12292052
Position Surface form Disambiguated ID Type / Status
Subject Pisae E292987 entity
Predicate hasLatinName P3646 FINISHED
Object Pisae E292987 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: Pisae | Statement: [Pisae, hasLatinName, Pisae]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pisae
Context triple: [Pisae, hasLatinName, Pisae]
  • A. Pisae chosen
    Pisae is the ancient Roman name for the city of Pisa in Tuscany, Italy, historically significant as a coastal settlement and later a prominent maritime republic.
  • B. Fusignano
    Fusignano is a small town in the Emilia-Romagna region of northern Italy, historically noted as the birthplace of Baroque composer Arcangelo Corelli.
  • C. Rosciano
    Rosciano is a small Italian municipality in the Abruzzo region, known for its rural landscape and traditional local agriculture.
  • D. San Savino
    San Savino is a small locality within the municipality of Predappio in the Emilia-Romagna region of northern Italy.
  • E. Ariccia
    Ariccia is a historic town in the Alban Hills near Rome, known for its Baroque architecture and traditional porchetta.
  • 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_69d6ab690ad081908c0ed3870ec82d53 completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d91d22ba488190914342fa7e69e159 completed April 10, 2026, 3:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69f634667db88190ac1368dc38daac73 completed May 2, 2026, 5:29 p.m.
Created at: April 8, 2026, 9:52 p.m.