Triple
T27691729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Page R sequencer |
E698177
|
entity |
| Predicate | runningOn |
P79620
|
FINISHED |
| Object | Fairlight CMI operating system |
—
|
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: Fairlight CMI operating system | Statement: [Page R sequencer, runningOn, Fairlight CMI operating system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runningOn Context triple: [Page R sequencer, runningOn, Fairlight CMI operating system]
-
A.
runsFrom
Indicates that one entity flees or escapes away from another entity.
-
B.
ranOn
chosen
Indicates that an entity executed or operated on a particular platform, system, or environment.
-
C.
runsUnder
Indicates that one process, task, or component operates within the control, environment, or context provided by another system, platform, or framework.
-
D.
runsMostly
Indicates that an entity performs running as its primary or most frequent activity compared to other activities.
-
E.
runsVia
Indicates that a process, operation, or connection is executed, routed, or carried out through a specified intermediate channel, path, or mechanism.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:52 p.m.