Triple
T3174688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hornets Venom GT |
E66433
|
entity |
| Predicate | competitiveDiscipline |
P45640
|
FINISHED |
| Object | basketball esports |
—
|
LITERAL 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: basketball esports | Statement: [Hornets Venom GT, competitiveDiscipline, basketball esports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitiveDiscipline Context triple: [Hornets Venom GT, competitiveDiscipline, basketball esports]
-
A.
competition
Indicates a relationship where two or more entities strive against each other to achieve a superior outcome, advantage, or reward.
-
B.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
C.
competitionFrom
Indicates that one entity is experiencing competitive pressure or rivalry originating from another entity.
-
D.
competitionClass
Indicates that one entity is classified into a particular competitive category or level within a competition or contest.
-
E.
competitionLevel
Indicates the degree or intensity of competitive pressure or rivalry present in a given context or interaction.
- F. None of above. chosen
Provenance (4 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_69ad8586a34c8190944c63ec11a8de1a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada670c800819098937783e2b05c7a |
completed | March 8, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_69ad9e02677c8190a21d93b1259b2761 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f7c21c819087e9992f5fe30a37 |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:06 p.m.