Triple
T25201802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FromSoftware |
E631141
|
entity |
| Predicate | platformHistory |
P159084
|
FINISHED |
| Object | PlayStation |
—
|
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 | Statement: [FromSoftware, platformHistory, PlayStation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformHistory Context triple: [FromSoftware, platformHistory, PlayStation]
-
A.
promotionHistory
Indicates the sequence of past promotions or advancement events that have occurred for an entity over time.
-
B.
operatorHistory
Indicates a record of past actions, states, or changes associated with a particular operator over time.
-
C.
storesHistory
Indicates that an entity retains or records past states, events, or changes over time related to another entity or process.
-
D.
upgradeHistory
Indicates the record of changes where one version, state, or configuration has been replaced or improved by another over time.
-
E.
estimatedHistory
Indicates that there is an inferred or approximated record of past states, events, or values associated with an entity or relationship.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 21, 2026, 12:51 p.m.