Triple
T9187997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AmigaDOS |
E220505
|
entity |
| Predicate | typicalUserScript |
P86719
|
FINISHED |
| Object | S:User-Startup |
—
|
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: S:User-Startup | Statement: [AmigaDOS, typicalUserScript, S:User-Startup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUserScript Context triple: [AmigaDOS, typicalUserScript, S:User-Startup]
-
A.
primaryScript
Indicates the writing system or script that is chiefly used to represent the language or content of an entity.
-
B.
typicalFunction
Indicates that something serves as the usual or characteristic function or role of an entity.
-
C.
typicalScriptForm
Indicates the usual or standard written script or notation in which something is commonly represented.
-
D.
addsScript
Indicates that one entity attaches or incorporates a script (code or instructions) into another entity, enabling additional behavior or functionality.
-
E.
scriptFeature
Indicates that a script includes, supports, or is characterized by a particular feature or capability.
- 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_69ca83e6d77c81909862b7afef56b1bf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc31d91d48190b8b8874e09c84404 |
completed | April 1, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc66d7bf648190b8bff5b584b84975 |
completed | April 1, 2026, 12:29 a.m. |
Created at: March 30, 2026, 7:24 p.m.