Triple
T17674479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YARV virtual machine |
E440610
|
entity |
| Predicate | contributor |
P1993
|
FINISHED |
| Object | Ruby core team |
—
|
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: Ruby core team | Statement: [YARV virtual machine, contributor, Ruby core team]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ruby core team Context triple: [YARV virtual machine, contributor, Ruby core team]
-
A.
Ruby core team
chosen
The Ruby core team is the group of developers responsible for maintaining and evolving the official Ruby programming language implementation and its core features.
-
B.
RSpec core team
The RSpec core team is the group of maintainers responsible for developing and overseeing the core components of the RSpec testing framework for Ruby.
-
C.
Ruby Port
Ruby Port is a young, fruit-forward fortified wine from Portugal’s Douro Valley, typically deep red in color and aged briefly in large casks to preserve its vibrant character.
-
D.
Hanami core team
The Hanami core team is the group of developers responsible for designing, building, and maintaining the Hanami Ruby web framework and its core components.
-
E.
Python core developers
Python core developers are the group of trusted contributors responsible for designing, implementing, and maintaining the official Python language and its reference implementation.
- 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_69e46f6ba22081909e2099490c047378 |
completed | April 19, 2026, 6 a.m. |
Created at: April 10, 2026, 10 a.m.