Triple
T6596450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amiga |
E148486
|
entity |
| Predicate | kernel |
P5103
|
FINISHED |
| Object | Exec |
E202463
|
NE 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: Exec | Statement: [Amiga, kernel, Exec]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Exec Context triple: [Amiga, kernel, Exec]
-
A.
Exec
chosen
Exec is the multitasking operating system kernel at the core of the Amiga computer platform, managing tasks, memory, and hardware resources.
-
B.
Cmd
Cmd is the standard abbreviation used for United Kingdom Command Papers, which are official government documents presented to Parliament.
-
C.
RUN
RUN is the National Rail station code assigned to Runcorn railway station in Cheshire, England.
-
D.
Home Command
Home Command was a major British Army formation responsible for the administration, training, and home defence of forces within the United Kingdom.
-
E.
Explorer.exe
Explorer.exe is the Windows graphical shell and file manager process that provides the desktop, taskbar, and file-browsing interface.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c687e7b8688190811ffee72e096468 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6aeecdd4c819092b87f4c91883154 |
completed | March 27, 2026, 4:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6e42fc9ec8190a6bb19010337d516 |
completed | March 27, 2026, 8:10 p.m. |
Created at: March 27, 2026, 1:56 p.m.