Triple

T18256530
Position Surface form Disambiguated ID Type / Status
Subject SNOBOL E437235 entity
Predicate hasVersion P455 FINISHED
Object SNOBOL1 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: SNOBOL1 | Statement: [SNOBOL, hasVersion, SNOBOL1]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SNOBOL1
Context triple: [SNOBOL, hasVersion, SNOBOL1]
  • A. SNOBOL chosen
    SNOBOL is an early high-level programming language from the 1960s known for its powerful pattern-matching and string-processing capabilities.
  • B. Algol 68S
    Algol 68S is a simplified subset of the Algol 68 programming language designed to make the language easier to implement and use.
  • C. Algol 68C
    Algol 68C is a compiler implementation of the Algol 68 programming language, designed to translate its advanced structured constructs into executable machine code.
  • D. Algol 68
    Algol 68 is a high-level, structured programming language from the ALGOL family, notable for its orthogonal design and influence on many later languages.
  • E. ALGOL
    ALGOL is a pioneering family of imperative computer programming languages from the late 1950s that introduced many foundational concepts in language design and heavily influenced later languages such as Pascal, C, and BASIC.
  • 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_69d8b913351c8190932b6a426de04b41 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4fd85ee548190a102611fcf709ad4 completed April 19, 2026, 4:06 p.m.
Created at: April 10, 2026, 10:34 a.m.