Triple
T27593256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gVisor |
E699829
|
entity |
| Predicate | isolates |
P110096
|
FINISHED |
| Object | container workloads from host kernel |
—
|
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: container workloads from host kernel | Statement: [gVisor, isolates, container workloads from host kernel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isolates Context triple: [gVisor, isolates, container workloads from host kernel]
-
A.
isolateFrom
chosen
Indicates that one entity is separated or kept apart from another entity or source.
-
B.
isolatedBy
Indicates that one entity has been separated or kept apart from another entity or set of entities, preventing interaction or influence between them.
-
C.
separates
Indicates that one entity divides, parts, or keeps other entities apart from each other.
-
D.
isolateWithin
Indicates that one entity is separated and contained inside the boundaries or context of another entity, limiting its interaction with the outside.
-
E.
colonizes
Indicates that one entity establishes control or settlement over another entity’s territory or domain, often imposing its presence, systems, or influence there.
- 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63055b96c8190b53a73a68c05c133 |
completed | May 2, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:06 p.m.