Triple
T37204391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Plutonia Experiment |
E922126
|
entity |
| Predicate | re-release |
P44033
|
FINISHED |
| Object | 2019 enhanced port by Bethesda |
—
|
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: 2019 enhanced port by Bethesda | Statement: [The Plutonia Experiment, re-release, 2019 enhanced port by Bethesda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: re-release Context triple: [The Plutonia Experiment, re-release, 2019 enhanced port by Bethesda]
-
A.
reRelease
chosen
Indicates that an entity is released again, typically representing a subsequent or updated release following an earlier one.
-
B.
reReleaseDate
Indicates the date on which something is released again, such as a reissued or updated version of an existing item.
-
C.
laterReReleasedBy
Indicates that an entity was re-released at a later time by a specified agent or organization.
-
D.
relaunch
Indicates restarting or bringing back into operation something that was previously launched, often with changes or improvements.
-
E.
releasedInsteadOf
Indicates that one entity was released in place of, or as a substitute for, another entity that was not released.
- 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_69f76ea4849481909b4a3073efb0114c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.