Triple

T21987877
Position Surface form Disambiguated ID Type / Status
Subject Brian Eno E543010 entity
Predicate familyName P18 FINISHED
Object Eno 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: Eno | Statement: [Brian Eno, familyName, Eno]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eno
Context triple: [Brian Eno, familyName, Eno]
  • A. Eno chosen
    Eno is a surname most famously associated with Brian Eno, the influential English musician, composer, and record producer known for pioneering ambient music.
  • B. Eno Division
    Eno Division is one of the main management and research sections of Duke Forest in North Carolina, encompassing forested land along the Eno River used for education, conservation, and scientific study.
  • C. Dalsey
    Dalsey is a surname most notably associated with Adrian Dalsey, one of the co-founders of the international courier company DHL.
  • D. Godrich
    Godrich is the surname of Nigel Godrich, the renowned English record producer best known for his work with Radiohead.
  • E. Moby
    Moby is an American electronic musician, producer, and DJ known for pioneering mainstream electronica in the 1990s with albums like "Play."
  • 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_69e0c48136b081908831fa907cc02e18 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f1270ad0d48190bd822289ce18195c completed April 28, 2026, 9:30 p.m.
Created at: April 16, 2026, 8:04 p.m.