Triple
T31892316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 639-3 |
E814176
|
entity |
| Predicate | hasChangeRequestProcess |
P9249
|
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: [ISO 639-3, hasChangeRequestProcess, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChangeRequestProcess Context triple: [ISO 639-3, hasChangeRequestProcess, yes]
-
A.
hasChangeControl
chosen
Indicates that an entity is subject to a defined process for reviewing, approving, and managing modifications or updates.
-
B.
hasProcess
Indicates that an entity is associated with, participates in, or is characterized by a particular process.
-
C.
hasPolicyChange
Indicates that a change has been made to an existing policy or set of policies affecting the related entities.
-
D.
changeRequestsImplementedBy
Indicates that the specified change requests have been carried out or fulfilled by the referenced implementing entity.
-
E.
hasResultingChange
Indicates that one entity causes or leads to a specific change or transformation in another entity or state.
- 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_69f348ef817481908440e2250319bcc8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: April 30, 2026, 11:58 p.m.