Triple
T30052528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RBD |
E763639
|
entity |
| Predicate | soldRecordsApprox |
P20940
|
FINISHED |
| Object | over 15 million |
—
|
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 15 million | Statement: [RBD, soldRecordsApprox, over 15 million]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soldRecordsApprox Context triple: [RBD, soldRecordsApprox, over 15 million]
-
A.
soldRecordsEstimate
chosen
Indicates an approximate number of sales transactions or records associated with an entity.
-
B.
soldWellIn
Indicates that something achieved strong sales performance within a particular market, region, or time period.
-
C.
soldAroundYear
Indicates that one entity was sold approximately in or around a specified year, rather than at an exact known date.
-
D.
soldDuring
Indicates that a selling transaction or event occurred within the time span of a specified period or event.
-
E.
soldUntil
Indicates that the availability or sale of an item continues up to, but not beyond, a specified time or date.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67a174b208190baa83258f93689f4 |
completed | May 2, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:55 p.m.