Triple
T9980085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenRC |
E196427
|
entity |
| Predicate | usesProcessSupervision |
P90297
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [OpenRC, usesProcessSupervision, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesProcessSupervision Context triple: [OpenRC, usesProcessSupervision, yes]
-
A.
usedProcess
Indicates that an entity employed or applied a particular process to achieve a result or perform an action.
-
B.
canSupervise
Indicates that one entity has the authority or capability to oversee, direct, or manage the work or activities of another entity.
-
C.
regulatesProcess
Indicates that one entity controls, modulates, or influences the occurrence, rate, or outcome of a process involving another entity.
-
D.
supervisionMechanism
chosen
Indicates that one entity oversees, monitors, or regulates the actions or behavior of another through a defined control or guidance process.
-
E.
supervisesFor
Indicates that one entity oversees, directs, or manages the work, activities, or responsibilities of another entity on behalf of a third party or specific purpose.
- 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_69ca82efbce081908179b4b9c65096eb |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb8b9aca881908a9b5dfd7e0de4ba |
completed | April 2, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:49 p.m.