Triple
T33093516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slinky |
E846845
|
entity |
| Predicate | hasSoldUnits |
P10648
|
FINISHED |
| Object | hundreds of millions |
—
|
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: hundreds of millions | Statement: [Slinky, hasSoldUnits, hundreds of millions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSoldUnits Context triple: [Slinky, hasSoldUnits, hundreds of millions]
-
A.
hasSoldOver
chosen
Indicates that one entity has sold a quantity of something exceeding a specified threshold or the amount sold by another entity.
-
B.
soldUntil
Indicates that the availability or sale of an item continues up to, but not beyond, a specified time or date.
-
C.
soldDuring
Indicates that a selling transaction or event occurred within the time span of a specified period or event.
-
D.
areSoldThrough
Indicates that items or services are made available to buyers via a particular sales channel, intermediary, or distribution method.
-
E.
soldProducts
Indicates that an entity has sold certain products to another entity or in a particular context.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 1, 2026, 1:26 a.m.