Triple
T21169091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woz Monitor |
E521644
|
entity |
| Predicate | bootBehavior |
P143140
|
FINISHED |
| Object | invoked on reset of Apple I |
—
|
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: invoked on reset of Apple I | Statement: [Woz Monitor, bootBehavior, invoked on reset of Apple I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bootBehavior Context triple: [Woz Monitor, bootBehavior, invoked on reset of Apple I]
-
A.
defaultBehavior
Indicates the standard or fallback way an entity acts or responds when no specific or overriding instructions or conditions are provided.
-
B.
unlockBehavior
Indicates that one entity enables access to or activates the behavior, functionality, or state of another entity.
-
C.
bedBehavior
Indicates how an entity typically acts, functions, or is used in relation to a bed.
-
D.
spaceBehavior
Indicates how an entity behaves, operates, or is arranged within a given space or spatial context.
-
E.
bootOption
Indicates the specific startup configuration or device choice used when a system boots.
- 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_69e0b50e30748190b186824a206d39b9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72711be9481909f16107b71d3500a |
completed | April 21, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3 p.m.