Triple
T1278246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | We Belong Together |
E27263
|
entity |
| Predicate | globalSales |
P22826
|
FINISHED |
| Object | over 6,000,000 copies |
—
|
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: over 6,000,000 copies | Statement: [We Belong Together, globalSales, over 6,000,000 copies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: globalSales Context triple: [We Belong Together, globalSales, over 6,000,000 copies]
-
A.
salesWorldwide
chosen
Indicates a relationship where an entity’s sales figures or activities are measured, reported, or occur across multiple countries or global markets.
-
B.
usedWorldwide
Indicates that something is utilized or applied across many countries or regions around the world.
-
C.
boxOfficeGrossUSD
Indicates the total amount of money an entity earned at the box office, expressed in U.S. dollars.
-
D.
hasGlobalReach
Indicates that an entity’s influence, operations, or impact extends across multiple countries or worldwide.
-
E.
globalRanking
Indicates the position or status of an entity relative to all comparable entities worldwide according to some ranking criteria.
- 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_69a496d3710c8190955dee8bc0dacb50 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c31602b8819087a57e8d390cae7a |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4bee0be808190a8ccac6a41851fdd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.