Triple
T30802043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Original Amiga File System |
E784394
|
entity |
| Predicate | stillUsableWith |
P27206
|
FINISHED |
| Object | Amiga emulators |
—
|
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: Amiga emulators | Statement: [Original Amiga File System, stillUsableWith, Amiga emulators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stillUsableWith Context triple: [Original Amiga File System, stillUsableWith, Amiga emulators]
-
A.
stillUsedBy
chosen
Indicates that something continues to be used or relied upon by another entity at the present time.
-
B.
canBeUsed
Indicates that one entity is suitable or available to serve a particular function, purpose, or role in relation to another entity or context.
-
C.
isRepairable
Indicates that an entity can be restored to proper working condition through repair.
-
D.
usableAs
Indicates that one entity can function in place of or serve the purpose of another entity.
-
E.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6903b80208190a98e2ca20c05fe70 |
completed | May 3, 2026, midnight |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:42 p.m.