Triple

T12035783
Position Surface form Disambiguated ID Type / Status
Subject Sorano E286533 entity
Predicate locatedNear P294 FINISHED
Object Sovana E265513 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: Sovana | Statement: [Sorano, locatedNear, Sovana]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sovana
Context triple: [Sorano, locatedNear, Sovana]
  • A. Sovana chosen
    Sovana is a small medieval village in southern Tuscany, Italy, renowned for its well-preserved historic center and nearby Etruscan archaeological sites.
  • B. Leova
    Leova is a small town in southwestern Moldova known for its location near the border with Romania and its position along the Prut River.
  • C. Solvan
    Solvan is a river associated with the town of Lons-le-Saunier in the Jura department of eastern France.
  • D. Saravena
    Saravena is a Colombian town and municipality located in the northeastern oil-producing and conflict-affected region near the border with Venezuela.
  • E. Nolana
    Nolana is a genus of flowering plants native mainly to coastal regions of South America, known for their showy, often blue, funnel-shaped blossoms.
  • 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_69d6ab4669e48190b59246358b0383ab completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d90408cbf0819093270c9833ef149a completed April 10, 2026, 2:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69f49d7d453c8190a27c5feca8f38991 completed May 1, 2026, 12:33 p.m.
Created at: April 8, 2026, 9:47 p.m.