Triple
T36895350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System 7.5.2 |
E911874
|
entity |
| Predicate | bootableOn |
P31985
|
FINISHED |
| Object | Power Macintosh 6100 series |
—
|
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: Power Macintosh 6100 series | Statement: [System 7.5.2, bootableOn, Power Macintosh 6100 series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bootableOn Context triple: [System 7.5.2, bootableOn, Power Macintosh 6100 series]
-
A.
bootMedium
chosen
Indicates that one entity serves as the medium or device from which another entity is booted or started.
-
B.
bootFeature
Indicates that an entity provides or is associated with a specific feature or capability available at system boot time.
-
C.
supportsUEFIBoot
Indicates that an entity is capable of initiating or handling the system startup process using UEFI (Unified Extensible Firmware Interface) boot mode.
-
D.
bootOption
Indicates the specific startup configuration or device choice used when a system boots.
-
E.
bootIndicator
Indicates that a system, device, or component is in a state or condition related to its startup or boot process.
- 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_69f76e841b54819097e7fa768bbc70b2 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd8d3ad08190854b227055102a89 |
completed | May 5, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.