Triple

T18117430
Position Surface form Disambiguated ID Type / Status
Subject Charles III of Naples E433641 entity
Predicate title P38 FINISHED
Object Rex Neapolis 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: Rex Neapolis | Statement: [Charles III of Naples, title, Rex Neapolis]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rex Neapolis
Context triple: [Charles III of Naples, title, Rex Neapolis]
  • A. Rex Neapolis chosen
    Rex Neapolis is a historical royal title associated with the kingship of Naples in the Italian peninsula.
  • B. Rex Merciorum
    Rex Merciorum is the Latin royal title meaning "King of the Mercians," historically associated with rulers of the Anglo-Saxon kingdom of Mercia such as Offa.
  • C. Rex Scottorum
    Rex Scottorum is the Latin royal title meaning "King of the Scots," historically used by Scottish monarchs such as Alexander I.
  • D. Rex Aragonum
    Rex Aragonum is the Latin royal title meaning "King of Aragon," historically borne by monarchs such as Peter the Great of Aragon.
  • E. Rex Galleciae
    Rex Galleciae is the Latin royal title meaning "King of Galicia," historically used for rulers such as Ordoño II of León who held authority over the Kingdom of Galicia in the medieval Iberian Peninsula.
  • 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_69d8b909e8cc81908df4cc2b8ea6d11f completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4ddd737708190863fba97cdc20d88 completed April 19, 2026, 1:51 p.m.
Created at: April 10, 2026, 10:28 a.m.