Triple
T14336075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cloud9 |
E355469
|
entity |
| Predicate | hasTeamName |
P744
|
FINISHED |
| Object | Cloud9 Blue |
E355469
|
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: Cloud9 Blue | Statement: [Cloud9, hasTeamName, Cloud9 Blue]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cloud9 Blue Context triple: [Cloud9, hasTeamName, Cloud9 Blue]
-
A.
Cloud9
chosen
Cloud9 is a prominent North American esports organization best known for its success across games like League of Legends, Counter-Strike, and Valorant.
-
B.
DigitalOcean
DigitalOcean is a cloud infrastructure provider known for its simple, developer-friendly platform offering virtual servers, storage, and networking services.
-
C.
Loudcloud
Loudcloud was a pioneering early-2000s cloud and managed hosting company co-founded by Marc Andreessen that later evolved into the software firm Opsware.
-
D.
Heroku
Heroku is a cloud platform as a service (PaaS) that enables developers to build, run, and scale applications without managing underlying infrastructure.
-
E.
Cloud Foundry
Cloud Foundry is an open-source, multi-cloud application platform-as-a-service (PaaS) that automates the deployment, scaling, and management of cloud-native applications.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8c2241e48190a0c626b3d741966a |
completed | April 14, 2026, 6:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd46986758819088750150ad47bae1 |
completed | May 8, 2026, 2:12 a.m. |
Created at: April 10, 2026, 1:14 a.m.