Triple
T28898914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R-Type |
E732900
|
entity |
| Predicate | hasRemakeOrCollection |
P21944
|
FINISHED |
| Object | R-Type Dimensions |
—
|
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: R-Type Dimensions | Statement: [R-Type, hasRemakeOrCollection, R-Type Dimensions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRemakeOrCollection Context triple: [R-Type, hasRemakeOrCollection, R-Type Dimensions]
-
A.
hasRemake
chosen
Indicates that one work is a new version or recreation of an earlier existing work.
-
B.
hasRemakeOrRetroVersion
Indicates that one work has been remade or re-released in a retro-style version of the original.
-
C.
appearsInRemakeOf
Indicates that an entity appears in a work that is a remake of another original work.
-
D.
remakeAppearsIn
Indicates that a remake of a work is featured, shown, or included within a particular context, such as a collection, series, or medium.
-
E.
appearsInRemakeAs
Indicates that an entity reappears in a remake version of a work, typically in a similar or related role as in the original.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69ff8cecbf048190860b9f72b8753f5c |
completed | May 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69ff8c4c39dc8190b5bf35adc1bae7c6 |
completed | May 9, 2026, 7:34 p.m. |
Created at: April 28, 2026, 8:01 a.m.