Triple
T17675022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elixir Core Team |
E440623
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | Elixir 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: Elixir Core Team | Statement: [Elixir Core Team, name, Elixir Core Team]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Elixir Core Team Context triple: [Elixir Core Team, name, Elixir Core Team]
-
A.
Elixir Core Team
chosen
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.
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.
-
C.
Svelte core team
The Svelte core team is the group of developers responsible for designing, maintaining, and advancing the Svelte framework and its official tooling.
-
D.
Ethereum core developers
Ethereum core developers are the group of engineers and researchers responsible for designing, maintaining, and upgrading the Ethereum blockchain protocol.
-
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.
- 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.