Triple
T13801974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TTWO |
E331662
|
entity |
| Predicate | issuerMainRevenueSource |
P13615
|
FINISHED |
| Object | video game sales |
—
|
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: video game sales | Statement: [TTWO, issuerMainRevenueSource, video game sales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuerMainRevenueSource Context triple: [TTWO, issuerMainRevenueSource, video game sales]
-
A.
majorRevenueSource
Indicates that one entity serves as the primary or dominant source of revenue for another entity.
-
B.
revenueSources
chosen
Indicates the relationship identifying where an entity’s revenue comes from or the different streams that generate its income.
-
C.
issuerBestKnownFor
Indicates the primary work, achievement, or characteristic for which an issuer is most widely recognized.
-
D.
issuerOriginalBusiness
Indicates that an entity is the original business organization that issued or created another entity (such as a document, instrument, or product).
-
E.
issuerBusinessType
Indicates the category or nature of business activity that the issuing entity is engaged in.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de025ded6c8190851c108ae559a355 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:12 p.m.