Triple

T17674634
Position Surface form Disambiguated ID Type / Status
Subject MRI (Matz's Ruby Interpreter) E440614 entity
Predicate replacedExecutionModel P29646 FINISHED
Object AST tree-walking interpreter LITERAL 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: AST tree-walking interpreter | Statement: [MRI (Matz's Ruby Interpreter), replacedExecutionModel, AST tree-walking interpreter]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: replacedExecutionModel
Context triple: [MRI (Matz's Ruby Interpreter), replacedExecutionModel, AST tree-walking interpreter]
  • A. executionModel
    Indicates how a process, task, or operation is carried out or implemented, specifying the underlying method, strategy, or mechanism of its execution.
  • B. replacedProcess
    Indicates that one process has been substituted or superseded by another process.
  • C. replacedClass
    Indicates that one class has been superseded or substituted by another class, typically in a versioning or refactoring context.
  • D. replacedWith chosen
    Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
  • E. replacedSubsystem
    Indicates that one subsystem has been substituted or exchanged for another, taking over its role or function.
  • F. None of above.

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_69d8b9e87e18819087104a44dc4dc5b1 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e46f6ba22081909e2099490c047378 completed April 19, 2026, 6 a.m.
PD Predicate disambiguation batch_69e3cde007d8819090dd92eea9f022cc completed April 18, 2026, 6:30 p.m.
Created at: April 10, 2026, 10 a.m.