Triple

T3244410
Position Surface form Disambiguated ID Type / Status
Subject Sergey Brin E68037 entity
Predicate familyName P18 FINISHED
Object Brin E68037 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: Brin | Statement: [Sergey Brin, familyName, Brin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Brin
Context triple: [Sergey Brin, familyName, Brin]
  • A. Brin chosen
    Brin is a surname most prominently associated with Sergey Brin, the co-founder of Google and a leading figure in the technology industry.
  • B. Brion
    Brion is a surname most notably associated with American musician, composer, and record producer Jon Brion.
  • C. Brylin
    Brylin is the surname of Sergei Brylin, a former Russian professional ice hockey player and three-time Stanley Cup champion with the New Jersey Devils.
  • D. Redfield
    Redfield is a surname of English origin borne by various notable individuals across fields such as politics, science, and the arts.
  • E. Hayden
    Hayden is a surname most notably associated with American actor and author Sterling Hayden, known for his roles in classic mid-20th-century films.
  • 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_69ad858e4c708190aa31d486cfee8a6a completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69adaf1982448190b3d60c9e4471421f completed March 8, 2026, 5:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69b2775be7c88190ba60b191f1c51e19 completed March 12, 2026, 8:20 a.m.
Created at: March 8, 2026, 3:08 p.m.