Triple

T2659106
Position Surface form Disambiguated ID Type / Status
Subject Romeo Montague E54683 entity
Predicate familyName P18 FINISHED
Object Montague E189603 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: Montague | Statement: [Romeo Montague, familyName, Montague]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Montague
Context triple: [Romeo Montague, familyName, Montague]
  • A. Montague chosen
    Montague is an English surname historically associated with the noble Montagu family and widely recognized from its use in literature, most notably in Shakespeare’s "Romeo and Juliet."
  • B. Abingdon
    Abingdon is a historic market town in Oxfordshire, England, often claimed to be one of the oldest continuously inhabited towns in the country.
  • C. Portchester
    Portchester is a village in Hampshire, England, known for its historic Roman fort and as the birthplace of author Neil Gaiman.
  • D. Morley
    Morley is a town in West Yorkshire, England, situated between Leeds and Bradford within the Leeds City Council metropolitan area.
  • E. Ratcliffe
    Ratcliffe is a surname most commonly associated with various historical figures, places, and buildings in English-speaking countries.
  • 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_69ab49e028948190b97e01d73548b1d9 completed March 6, 2026, 9:40 p.m.
NER Named-entity recognition batch_69abd94dcaa48190aec625f68ce61a02 completed March 7, 2026, 7:52 a.m.
NED1 Entity disambiguation (via context triple) batch_69af98d765c48190a227137467b7dbe1 completed March 10, 2026, 4:06 a.m.
Created at: March 6, 2026, 9:53 p.m.