Triple
T30657545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | THQ |
E780423
|
entity |
| Predicate | hadSuccessWithPlatform |
P169985
|
FINISHED |
| Object | PlayStation 2 |
—
|
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 2 | Statement: [THQ, hadSuccessWithPlatform, PlayStation 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadSuccessWithPlatform Context triple: [THQ, hadSuccessWithPlatform, PlayStation 2]
-
A.
isSuccessful
Indicates that an action, process, or attempt has achieved its intended goal or outcome.
-
B.
succeededUnder
Indicates that one entity achieved success or attained a position while operating under the authority, leadership, or conditions established by another entity.
-
C.
platformAcquired
Indicates that one entity has obtained ownership or control of a platform from another entity through an acquisition.
-
D.
hasPlatformOn
Indicates that one entity is physically supported by or situated on the surface or structure of another entity.
-
E.
adoptedPlatformOn
Indicates that an entity began using or officially adopted a particular platform on a specific date or point in time.
- F. None of above. chosen
Provenance (4 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_69f224a6d10481909290be1a00fc83b3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68ade49d48190a80182cf054bd154 |
completed | May 2, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 29, 2026, 8:30 p.m.