Triple
T17675454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Active Support |
E440631
|
entity |
| Predicate | compatibleWith |
P203
|
FINISHED |
| Object | TruffleRuby |
—
|
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: TruffleRuby | Statement: [Active Support, compatibleWith, TruffleRuby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TruffleRuby Context triple: [Active Support, compatibleWith, TruffleRuby]
-
A.
TruffleRuby
chosen
TruffleRuby is a high-performance implementation of the Ruby programming language built on the GraalVM platform, aiming to provide faster execution and improved tooling compatibility.
-
B.
Matz's Ruby Interpreter
Matz's Ruby Interpreter is the original and most widely used reference implementation of the Ruby programming language, created by Yukihiro "Matz" Matsumoto.
-
C.
Rubinius
Rubinius is an alternative Ruby implementation featuring a virtual machine and just-in-time compilation, designed for high performance and concurrency.
-
D.
JRuby
JRuby is a high-performance implementation of the Ruby programming language that runs on the Java Virtual Machine and integrates with Java libraries.
-
E.
Ruby 3.x
Ruby 3.x is a major modern release of the Ruby programming language focused on performance improvements, concurrency features, and enhanced developer productivity.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f6cca54819094ea0bed1517724e |
completed | April 19, 2026, 6 a.m. |
Created at: April 10, 2026, 10 a.m.