Triple
T25933557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IMSAI 8080 |
E653490
|
entity |
| Predicate | powerSwitchLocation |
P43462
|
FINISHED |
| Object | front panel |
—
|
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 | Statement: [IMSAI 8080, powerSwitchLocation, front panel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerSwitchLocation Context triple: [IMSAI 8080, powerSwitchLocation, front panel]
-
A.
powerSwitchType
Indicates the specific kind or configuration of power switch associated with or used by an entity.
-
B.
powerSupplyLocation
chosen
Indicates the physical place or component where an entity’s electrical power is provided or connected.
-
C.
powerChange
Indicates a change in the level, amount, or state of power associated with an entity over time.
-
D.
powerCondition
Indicates that one entity’s ability to function, operate, or exert influence depends on a specified power-related requirement or state being satisfied.
-
E.
powerInterface
Indicates that one entity serves as a power-providing interface or connection point for another entity, enabling the transfer or supply of electrical power.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 22, 2026, 8:37 a.m.