Triple
T29101875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panzer Dragoon Saga |
E736656
|
entity |
| Predicate | reReleaseStatus |
P166326
|
FINISHED |
| Object | no modern digital re-release as of 2024 |
—
|
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: no modern digital re-release as of 2024 | Statement: [Panzer Dragoon Saga, reReleaseStatus, no modern digital re-release as of 2024]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reReleaseStatus Context triple: [Panzer Dragoon Saga, reReleaseStatus, no modern digital re-release as of 2024]
-
A.
reRelease
Indicates that an entity is released again, typically representing a subsequent or updated release following an earlier one.
-
B.
reReleaseLabel
Indicates that a work has been re-released under a different label than its original release.
-
C.
releaseStatus
Indicates the current state or phase of an item’s release process (e.g., planned, in progress, or completed).
-
D.
reReleaseDeveloper
Indicates that a developer is responsible for creating or overseeing a re-released version of a product or work.
-
E.
reReleaseDate
Indicates the date on which something is released again, such as a reissued or updated version of an existing item.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f661b64ea881908332bb86e9739cc4 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 11:12 a.m.