Triple
T2313396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Process PEP |
E51007
|
entity |
| Predicate | changeType |
P38005
|
FINISHED |
| Object | meta-process changes rather than code changes |
—
|
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: meta-process changes rather than code changes | Statement: [Process PEP, changeType, meta-process changes rather than code changes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changeType Context triple: [Process PEP, changeType, meta-process changes rather than code changes]
-
A.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
-
B.
changePolicy
Indicates that an entity modifies, replaces, or updates an existing policy governing rules, procedures, or behaviors.
-
C.
classificationChange
Indicates a change in the category, type, or status under which an entity is classified.
-
D.
changesEvery
Indicates that one entity undergoes a change whenever or each time another specified condition, event, or entity changes.
-
E.
typeOfAmendment
Indicates the specific kind or category of amendment that is being applied to something, such as a document, law, or agreement.
- 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_69a88b074b908190ae983dbca7757d88 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc58e88e481908733fdf79d3f8a15 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc682d094819081a96ffb77c4c42a |
completed | March 7, 2026, 6:32 a.m. |
Created at: March 4, 2026, 7:49 p.m.