Triple
T33910943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harley Quinn's Revenge |
E869309
|
entity |
| Predicate | releasePlatformFirst |
P17946
|
FINISHED |
| Object | PlayStation 3 |
—
|
NE NERFINISHED |
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: [Harley Quinn's Revenge, releasePlatformFirst, PlayStation 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releasePlatformFirst Context triple: [Harley Quinn's Revenge, releasePlatformFirst, PlayStation 3]
-
A.
firstReleasePlatform
chosen
Indicates the platform on which something (such as a product, work, or media) was first released.
-
B.
firstDeploymentPlatform
Indicates the platform on which something (such as a product, service, or software) was initially deployed or launched.
-
C.
platformFirstReleased
Indicates the date or time when a platform was initially released or made publicly available.
-
D.
releaseDateOnPlatform
Indicates the date on which a particular item (e.g., a product, game, or media) becomes available on a specific platform.
-
E.
initialReleaseFor
Indicates that one entity is the first or original release version associated with another entity (such as a work, product, or edition).
- 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_69f3499869bc8190b6c33a81686af226 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 1, 2026, 1:48 a.m.