Triple
T30405027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cell BE |
E773454
|
entity |
| Predicate | firstCommercialUseIn |
P203794
|
FINISHED |
| Object | PlayStation 3 |
E44203
|
NE 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: PlayStation 3 | Statement: [Cell BE, firstCommercialUseIn, PlayStation 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCommercialUseIn Context triple: [Cell BE, firstCommercialUseIn, PlayStation 3]
-
A.
firstCommercialUse
Indicates the earliest point in time at which something was used commercially or put into commercial operation.
-
B.
firstCommercialApplication
Indicates that an entity represents the earliest or initial commercial use or deployment of another entity (such as a technology, invention, or product).
-
C.
locationOfFirstCommercialUse
Indicates the place where something was first used commercially.
-
D.
firstProminentUse
Indicates the earliest notable or widely recognized instance in which something was used in a significant or influential way.
-
E.
firstHistoricalUse
Indicates that the subject entity represents the earliest known or recorded instance of the object entity being used or occurring in history.
- F. None of above. chosen
Provenance (5 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0205c0bff481908238a382459b3a93 |
completed | May 11, 2026, 4:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a27ac0ecb0c8190a4095bdeaafb7e75 |
completed | June 9, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_6a0205143f20819087ee31576835be26 |
completed | May 11, 2026, 4:34 p.m. |
| PDg | Predicate description generation | batch_6a0205bfab208190982728a690ce183d |
completed | May 11, 2026, 4:37 p.m. |
Created at: April 29, 2026, 8:03 p.m.