Triple

T11958606
Position Surface form Disambiguated ID Type / Status
Subject AdaCore E284613 entity
Predicate specializesIn P3 FINISHED
Object Ada programming language E862634 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: Ada programming language | Statement: [AdaCore, specializesIn, Ada programming language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ada programming language
Context triple: [AdaCore, specializesIn, Ada programming language]
  • A. Ada
    Ada is a small village in northwest Ohio, known as the home of Ohio Northern University.
  • B. Ada
    Ada is a small city in south-central Oklahoma known as the county seat of Pontotoc County and home to East Central University and the headquarters of the Chickasaw Nation.
  • C. Ada
    Ada is a town in northern Serbia's Vojvodina region, known for its Hungarian ethnic majority and location along the Tisa River.
  • D. Ada
    Ada is a competitive boxer known for her performances in the ring.
  • E. Ada chosen
    Ada is a statically typed, high-level programming language designed with strong support for reliability, safety, and real-time systems, widely used in aerospace, defense, and other mission-critical applications.
  • 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_69d6ab2db38c8190b1f0ed6663ef8ada completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d903681a00819098c2b5260e2ef834 completed April 10, 2026, 2:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69f459210d1c8190953cd01da3d2ad04 completed May 1, 2026, 7:41 a.m.
Created at: April 8, 2026, 9:45 p.m.