Triple
T2977580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COSMAC ELF |
E80434
|
entity |
| Predicate | programEntryMethod |
P44371
|
FINISHED |
| Object | front-panel switch toggling |
—
|
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: front-panel switch toggling | Statement: [COSMAC ELF, programEntryMethod, front-panel switch toggling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programEntryMethod Context triple: [COSMAC ELF, programEntryMethod, front-panel switch toggling]
-
A.
programOn
Indicates that a program is scheduled to be broadcast or presented on a particular channel, station, platform, or device.
-
B.
mainEntranceOn
Indicates that the primary entrance of one entity is located on or faces toward another entity, such as a particular side, street, or boundary.
-
C.
entryPointFor
Indicates that one entity serves as the access or starting location through which another entity is entered, initiated, or reached.
-
D.
program
Indicates that an entity creates, writes, or develops a computer program or software application.
-
E.
programSequence
Indicates that one program or step occurs in a specific order directly before or after another within a defined sequence.
- 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad999b0d50819093dac7678b887a9b |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad96105a708190a9ec4838cbcb1207 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f5d28c8190899d90204dc43428 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:58 p.m.