Triple
T30504599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .TOS |
E776231
|
entity |
| Predicate | executableOn |
P11903
|
FINISHED |
| Object | Atari ST |
—
|
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: Atari ST | Statement: [.TOS, executableOn, Atari ST]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: executableOn Context triple: [.TOS, executableOn, Atari ST]
-
A.
executableName
Indicates the specific name of a program or binary file that is intended to be executed.
-
B.
canRunOn
chosen
Indicates that one entity is capable of operating, executing, or functioning on another entity (such as a platform, system, or environment).
-
C.
executionDevice
Indicates that an entity serves as the instrument, tool, or device used to carry out or execute a particular action or process.
-
D.
executionBy
Indicates that one entity carries out or performs the execution (killing or implementation of a death sentence) of another entity.
-
E.
executedWith
Indicates that an action or process was carried out using, accompanied by, or in conjunction with a specified tool, method, or participant.
- 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_69f2249a155c8190b1d512106007e9bb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 8:15 p.m.