Triple
T30801830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SiN (Amiga port) |
E784388
|
entity |
| Predicate | adaptedFromPlatform |
P172938
|
FINISHED |
| Object | 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: PC | Statement: [SiN (Amiga port), adaptedFromPlatform, PC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adaptedFromPlatform Context triple: [SiN (Amiga port), adaptedFromPlatform, PC]
-
A.
adoptedPlatformOn
Indicates that an entity began using or officially adopted a particular platform on a specific date or point in time.
-
B.
adaptsFrom
Indicates that one entity is derived, modified, or transformed from another, preserving core elements while changing form, medium, or context.
-
C.
replacedOnPlatformBy
Indicates that one entity has been superseded or taken over by another entity on a particular platform.
-
D.
originPlatform
Indicates the platform, system, or environment from which an entity, event, or piece of data originally comes.
-
E.
usedConvertedPlatformFrom
Indicates that an entity made use of another entity that had been converted from a specified original platform.
- 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_69f6b2d9aad88190a445f8f591cb19fc |
completed | May 3, 2026, 2:28 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b21da77081908c5c015c4606d344 |
completed | May 3, 2026, 2:25 a.m. |
Created at: April 29, 2026, 8:42 p.m.