Triple
T25372060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 9P network protocol |
E632955
|
entity |
| Predicate | canRunOver |
P11903
|
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: [9P network protocol, canRunOver, Unix domain sockets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canRunOver Context triple: [9P network protocol, canRunOver, Unix domain sockets]
-
A.
canOutrun
Indicates that one entity is able to run faster than another and thus surpass or escape it in a running context.
-
B.
canBeUsedOver
Indicates that one entity is suitable or valid for use in place of, or in relation to, another entity.
-
C.
canRunOn
chosen
Indicates that one entity is capable of operating, executing, or functioning on another entity (such as a platform, system, or environment).
-
D.
runsDirectlyOver
Indicates that one entity passes or extends immediately above another along its length or span, without significant vertical separation or intervening structures.
-
E.
canBeTransportedOver
Indicates that one entity is capable of being moved or carried across, along, or by means of another entity or medium.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4a11323e08190a8ec4687f8fefe7f |
completed | May 1, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:38 p.m.