Triple
T15131803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Active Edge |
E361437
|
entity |
| Predicate | requiresDeviceHardwareSupport |
P16207
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Active Edge, requiresDeviceHardwareSupport, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresDeviceHardwareSupport Context triple: [Active Edge, requiresDeviceHardwareSupport, true]
-
A.
requiresDevice
chosen
Indicates that performing the specified action or relationship is contingent on the presence or use of a particular device.
-
B.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
-
C.
requiresFirmware
Indicates that one entity depends on specific firmware being present or installed on another entity in order to function or be valid.
-
D.
supportsGPUType
Indicates that one entity is compatible with, or capable of operating using, a specified type of GPU.
-
E.
platformRequirement
Indicates that one entity specifies a necessary platform or environment condition that must be met for another entity to function or be applicable.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005b194748190801e3956bf2429d4 |
completed | April 15, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69deb9713fe881909dec2fd3f6c84b39 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:06 a.m.