Triple
T8610475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Firecracker |
E203901
|
entity |
| Predicate | deviceModel |
P83868
|
FINISHED |
| Object | paravirtualized devices only |
—
|
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: paravirtualized devices only | Statement: [Firecracker, deviceModel, paravirtualized devices only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deviceModel Context triple: [Firecracker, deviceModel, paravirtualized devices only]
-
A.
deviceIndicates
Indicates that a device provides a signal, status, or output that conveys information about a condition, event, or state.
-
B.
platformModel
Indicates that one entity serves as the underlying platform or foundational model upon which the other entity is built, operates, or depends.
-
C.
modelNumber
Indicates that one entity is the specific model identifier or code assigned to another entity (such as a product or device).
-
D.
device
Indicates that one entity is a device used, controlled, or referenced by another entity in the relationship.
-
E.
testedDevice
Indicates that one entity has performed a test on, or experimentally evaluated, another entity as a device.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46ee96ac8190809817c403da2889 |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:25 p.m.