Triple
T17675855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RSpec Story Runner |
E440640
|
entity |
| Predicate | maintainerCommunity |
P55130
|
FINISHED |
| Object | RSpec core team |
—
|
NE NERFINISHED |
How this triple was built (3 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: RSpec core team | Statement: [RSpec Story Runner, maintainerCommunity, RSpec core team]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RSpec core team Context triple: [RSpec Story Runner, maintainerCommunity, RSpec core team]
-
A.
Elixir Core Team
The Elixir Core Team is the group of maintainers and lead contributors responsible for designing, developing, and stewarding the Elixir programming language and its ecosystem.
-
B.
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.
-
C.
Solidity core team
The Solidity core team is the group of primary developers and maintainers responsible for designing, implementing, and evolving the Solidity smart contract programming language.
-
D.
Babel core team
The Babel core team is the group of developers responsible for designing, implementing, and maintaining the Babel JavaScript compiler and its ecosystem.
-
E.
Laravel core team
The Laravel core team is the group of developers responsible for designing, developing, and overseeing the official Laravel PHP framework and its ecosystem.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RSpec core team Target entity description: The RSpec core team is the group of maintainers responsible for developing and overseeing the core components of the RSpec testing framework for Ruby.
-
A.
Elixir Core Team
The Elixir Core Team is the group of maintainers and lead contributors responsible for designing, developing, and stewarding the Elixir programming language and its ecosystem.
-
B.
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.
-
C.
Solidity core team
The Solidity core team is the group of primary developers and maintainers responsible for designing, implementing, and evolving the Solidity smart contract programming language.
-
D.
Babel core team
The Babel core team is the group of developers responsible for designing, implementing, and maintaining the Babel JavaScript compiler and its ecosystem.
-
E.
Laravel core team
The Laravel core team is the group of developers responsible for designing, developing, and overseeing the official Laravel PHP framework and its ecosystem.
- F. None of above. chosen
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_69d8b9e940b081908b862bb0e6e89b0d |
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.