Triple
T28610995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | qemu-ga |
E724166
|
entity |
| Predicate | typicallyRunsAs |
P23495
|
FINISHED |
| Object | daemon |
—
|
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: daemon | Statement: [qemu-ga, typicallyRunsAs, daemon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyRunsAs Context triple: [qemu-ga, typicallyRunsAs, daemon]
-
A.
runsUnder
chosen
Indicates that one process, task, or component operates within the control, environment, or context provided by another system, platform, or framework.
-
B.
runsByDefault
Indicates that an action, process, or behavior is executed automatically without requiring explicit configuration or invocation.
-
C.
startupRole
Indicates that an entity holds a specific role or position within a startup organization.
-
D.
systemRole
Indicates the functional position or responsibility that an entity holds within a larger system or structure.
-
E.
usesCredentialsOf
Indicates that one entity authenticates or operates by employing the credentials (such as login details, tokens, or keys) that belong to another entity.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a00ca5e907481909d391afd55938a1b |
completed | May 10, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_6a00ca2214348190a674a85ede709e2e |
completed | May 10, 2026, 6:10 p.m. |
Created at: April 28, 2026, 4:30 a.m.