Triple
T28616222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SetEnvironmentVariable |
E724278
|
entity |
| Predicate | affectsScope |
P132368
|
FINISHED |
| Object | current process |
—
|
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: current process | Statement: [SetEnvironmentVariable, affectsScope, current process]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectsScope Context triple: [SetEnvironmentVariable, affectsScope, current process]
-
A.
hasInfluenceScope
Indicates the range or extent within which an entity’s influence, impact, or authority is effective or applicable.
-
B.
coverageScope
Indicates the extent or range of entities, conditions, or situations that are included under a particular coverage or applicability.
-
C.
impactScope
chosen
Indicates the extent or range within which an action, event, or entity produces effects or consequences.
-
D.
areAffectedBy
Indicates that one entity experiences an effect, influence, or impact as a result of another entity or event.
-
E.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
- 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_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 28, 2026, 4:32 a.m.