Triple
T30801833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SiN (Amiga port) |
E784388
|
entity |
| Predicate | requiresOriginalDataFilesFrom |
P196625
|
FINISHED |
| Object | SiN (PC) |
—
|
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: SiN (PC) | Statement: [SiN (Amiga port), requiresOriginalDataFilesFrom, SiN (PC)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresOriginalDataFilesFrom Context triple: [SiN (Amiga port), requiresOriginalDataFilesFrom, SiN (PC)]
-
A.
hasOriginalVersion
Indicates that one entity is the original or initial version from which another entity is derived or adapted.
-
B.
hasExplicitOriginal
Indicates that something has a clearly specified, directly stated original source or version from which it is derived.
-
C.
originalFor
Indicates that one entity serves as the source, basis, or prototype from which another entity is derived, adapted, or created.
-
D.
locationOfOriginals
Indicates the place where the original versions or source items of something are kept or found.
-
E.
originalResource
Indicates that one resource serves as the source, predecessor, or basis from which another resource is derived or adapted.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
| PDg | Predicate description generation | batch_69fe5ec84910819094cb15269ace7c51 |
completed | May 8, 2026, 10:08 p.m. |
Created at: April 29, 2026, 8:42 p.m.