Triple

T7136732
Position Surface form Disambiguated ID Type / Status
Subject Charles Boyle, 4th Earl of Orrery E166323 entity
Predicate familyName P18 FINISHED
Object Boyle E111086 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: Boyle | Statement: [Charles Boyle, 4th Earl of Orrery, familyName, Boyle]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Boyle
Context triple: [Charles Boyle, 4th Earl of Orrery, familyName, Boyle]
  • A. Boyle chosen
    Boyle is a surname of Irish origin most famously associated with the 17th-century natural philosopher and chemist Robert Boyle, a pioneer of modern experimental science.
  • B. Boyle
    Boyle is the vehicle registration prefix code used on license plates issued in Boyle County, Kentucky.
  • C. Boyle
    Boyle is a small historic town in western Ireland known for landmarks like Boyle Abbey and its scenic setting near Lough Key in County Roscommon.
  • D. Boylan
    Boylan is the surname of Blazes Boylan, a character in James Joyce’s novel "Ulysses."
  • E. Davy
    Davy is a familiar diminutive form of the given name David, often used as a casual or affectionate nickname.
  • 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_69c68884a9388190af42f90d1c1a7151 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e6926d748190bc8c150fc1860531 completed March 27, 2026, 8:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7a348a748819082f87039ea79f251 completed March 28, 2026, 9:45 a.m.
Created at: March 27, 2026, 2:45 p.m.