Triple

T22499180
Position Surface form Disambiguated ID Type / Status
Subject Certbot E556222 entity
Predicate developer P73 FINISHED
Object EFF 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: EFF | Statement: [Certbot, developer, EFF]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: EFF
Context triple: [Certbot, developer, EFF]
  • A. EFF chosen
    EFF is a leading nonprofit organization that defends civil liberties, privacy, and free expression in the digital world.
  • B. EF
    EF is the commonly used abbreviation for the Eclipse Foundation, a nonprofit organization that oversees open-source software projects and the Eclipse IDE ecosystem.
  • C. EF
    EF is the commonly used abbreviation for the Ethereum Foundation, the nonprofit organization that supports the development and growth of the Ethereum blockchain ecosystem.
  • D. EF
    EF is the vehicle registration code used on license plates for the German city of Erfurt.
  • E. EFDD
    EFDD is a former eurosceptic political group in the European Parliament that brought together parties critical of European Union integration and supportive of national sovereignty and direct democracy.
  • 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_69e11e5445bc8190b6a9481926db3355 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15cb3deb88190874230ae06a352d6 completed April 29, 2026, 1:19 a.m.
Created at: April 16, 2026, 8:50 p.m.