Triple
T11655169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | runc |
E276996
|
entity |
| Predicate | supportsNamespaceIsolation |
P68771
|
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: [runc, supportsNamespaceIsolation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNamespaceIsolation Context triple: [runc, supportsNamespaceIsolation, true]
-
A.
hasNamespace
Indicates that one entity is associated with, defined within, or belongs to a particular namespace context provided by another entity.
-
B.
hasNamespaces
Indicates that an entity is associated with one or more namespaces that define its scoping or organizational context.
-
C.
hasIsolation
Indicates that an entity is separated or kept apart from others, typically to prevent interaction, influence, or contamination.
-
D.
isDynamicallyIsolated
chosen
Indicates that an entity operates in a separate, runtime-enforced context or environment such that its state, behavior, or side effects are prevented from directly affecting or being affected by other entities.
-
E.
isIsolated
Indicates that an entity exists or occurs separately from others, without direct contact, interaction, or connection.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3cee010819089cffdbefe5a6efb |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.