Triple
T20281412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoenix |
E503151
|
entity |
| Predicate | developer |
P73
|
FINISHED |
| Object | Phoenix Core Team |
E1282073
|
NE 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: Phoenix Core Team | Statement: [Phoenix, developer, Phoenix Core Team]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Phoenix Core Team Context triple: [Phoenix, developer, Phoenix Core Team]
-
A.
Phoenix Core Team
chosen
The Phoenix Core Team is the group of developers responsible for designing and maintaining Phoenix, the popular web framework built on the Elixir programming language.
-
B.
Hex Core Team
The Hex Core Team is the group responsible for developing and maintaining Hex, the package manager and repository ecosystem for the Elixir and Erlang communities.
-
C.
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.
-
D.
Phoenix Consortium
Phoenix Consortium was the investment group that acquired the British car manufacturer Rover Group in the mid-1990s.
-
E.
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69e0b4b0e79c8190bd61f22ef1329fa8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6768e9f0881909c8fe8772dafd468 |
completed | April 20, 2026, 6:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a085a25e5f08190b11cbcbdda42113b |
completed | May 16, 2026, 11:51 a.m. |
Created at: April 16, 2026, 10:38 a.m.