Triple
T2629146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wayland |
E59591
|
entity |
| Predicate | usesIPC |
P42337
|
FINISHED |
| Object | Unix domain sockets |
—
|
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: Unix domain sockets | Statement: [Wayland, usesIPC, Unix domain sockets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesIPC Context triple: [Wayland, usesIPC, Unix domain sockets]
-
A.
usesIntervention
Indicates that one entity applies, employs, or relies on a specific intervention (such as a treatment, method, or strategy) in relation to another entity or context.
-
B.
usesInterface
Indicates that one entity interacts with or operates another entity through a specified interface or set of interface methods.
-
C.
usesInfrastructure
Indicates that one entity makes use of, depends on, or operates through the infrastructure provided or managed by another entity.
-
D.
usesDRS
Indicates that one entity employs or relies on a specific Decision Review System (DRS) for evaluation, verification, or decision-making purposes.
-
E.
usedProcess
Indicates that an entity employed or applied a particular process to achieve a result or perform an action.
- 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_69ab4ac8596c8190b34997e73d9e991c |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abdb0e7b888190bfa5d2e33f00ec0f |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd810d7f481908e81c305772c4c14 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abdb0bf9b881908b239c1310c7bbf3 |
completed | March 7, 2026, 8 a.m. |
Created at: March 6, 2026, 9:50 p.m.