Triple
T11541754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Call of Duty League |
E273691
|
entity |
| Predicate | hasPrizePool |
P72606
|
FINISHED |
| Object | multi-million USD |
—
|
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: multi-million USD | Statement: [Call of Duty League, hasPrizePool, multi-million USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrizePool Context triple: [Call of Duty League, hasPrizePool, multi-million USD]
-
A.
prizePool
Indicates that a certain amount of rewards or funds is collectively available to be distributed among participants in an event, competition, or activity.
-
B.
hasPrizeMoney
chosen
Indicates that an entity awards, offers, or is associated with a specified amount of prize money.
-
C.
hasGrandPrize
Indicates that an entity possesses, is awarded, or is associated with a grand prize in a given context.
-
D.
hasMoonPool
Indicates that an object, structure, or facility includes or is equipped with a moon pool (an opening in its floor giving direct access to the water below).
-
E.
hasAwardPeriod
Indicates the time span or date range during which an award is valid, active, or applicable.
- F. None of above.
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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e09eec8190894069d86b79183d |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d80879fdb48190be6dacc8aa63c809 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.