Triple
T321651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iSCSI |
E6426
|
entity |
| Predicate | encapsulates |
P1393
|
FINISHED |
| Object | SCSI command descriptor blocks |
—
|
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: SCSI command descriptor blocks | Statement: [iSCSI, encapsulates, SCSI command descriptor blocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encapsulates Context triple: [iSCSI, encapsulates, SCSI command descriptor blocks]
-
A.
encodedIn
Indicates that one entity is represented, stored, or expressed within another entity using a specific encoding or format.
-
B.
protects
Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
-
C.
ensures
Indicates that one entity guarantees or makes certain that a particular condition, outcome, or state holds for another entity or situation.
-
D.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
E.
integrates
Indicates that one entity combines or brings together another entity or set of entities into a unified, functioning whole.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea81a1e88190b3496070eb3d85f5 |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e948048c819098ba4de9261ef2ef |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.