Triple

T17601100
Position Surface form Disambiguated ID Type / Status
Subject Novilara inscriptions E428702 entity
Predicate locatedIn P40 FINISHED
Object Novilara NE NERFINISHED

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: Novilara | Statement: [Novilara inscriptions, locatedIn, Novilara]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Novilara
Context triple: [Novilara inscriptions, locatedIn, Novilara]
  • A. Novilara chosen
    Novilara is an archaeological site and locality in the Marche region of Italy, known for its ancient Picene culture remains and notable funerary stelae.
  • B. Loelva
    Loelva is a river flowing through Norway’s scenic Loen valley, known for its glacial origins and striking turquoise waters.
  • C. Nivala
    Nivala is a small town and municipality in Northern Ostrobothnia, Finland, known for its rural character and agricultural surroundings.
  • 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. Arnara
    Arnara is a small municipality in the Lazio region of central Italy, located in the province of Frosinone.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d889e1c6148190ba76241e74688f8b completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46c48dfc08190ba360e6082cffa87 completed April 19, 2026, 5:46 a.m.
Created at: April 10, 2026, 5:51 a.m.