Triple

T8393479
Position Surface form Disambiguated ID Type / Status
Subject Neapolis E197997 entity
Predicate hasRomanName P6662 FINISHED
Object Flavia Neapolis E113927 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: Flavia Neapolis | Statement: [Neapolis, hasRomanName, Flavia Neapolis]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Flavia Neapolis
Context triple: [Neapolis, hasRomanName, Flavia Neapolis]
  • A. Flavia Neapolis chosen
    Flavia Neapolis was a Roman city in Samaria, founded in the 1st century CE near ancient Shechem and known today as Nablus in the West Bank.
  • B. Flavia Caesariensis
    Flavia Caesariensis was a late Roman province in Britain, established during the administrative reforms of the 3rd–4th centuries CE.
  • C. Aurelianum
    Aurelianum is the ancient Latin name for the French city of Orléans, reflecting its origins as a Roman settlement.
  • D. Ulpia
    Ulpia is a Latin name element commonly associated with Roman imperial and colonial foundations, particularly linked to Emperor Trajan’s family name Ulpius.
  • E. Flavia
    Flavia is a feminine given name of Latin origin, historically used in ancient Rome and derived from the family name Flavius.
  • 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_69ca82f816bc8190ab321c07d72208c1 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb8184788081909e9857afff629985 completed March 31, 2026, 8:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69ce02d5e0648190b33011c2ddca4ad3 completed April 2, 2026, 5:47 a.m.
Created at: March 30, 2026, 6:03 p.m.