Triple
T12207348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITIL |
E290868
|
entity |
| Predicate | coversProcessArea |
P61123
|
FINISHED |
| Object | incident management |
—
|
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: incident management | Statement: [ITIL, coversProcessArea, incident management]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversProcessArea Context triple: [ITIL, coversProcessArea, incident management]
-
A.
coversPolicyArea
Indicates that a policy, document, or initiative includes or addresses a particular policy area or topic within its scope.
-
B.
includesCapabilityArea
Indicates that one entity encompasses or contains a specific capability area as part of its overall scope or functionality.
-
C.
coversAspect
chosen
Indicates that one entity addresses, includes, or deals with a particular aspect or facet of another entity or topic.
-
D.
coverageModel
Indicates a relationship where a specific model or framework defines, structures, or governs the extent and manner in which something is covered or addressed.
-
E.
oversawProgramArea
Indicates that one entity had managerial or supervisory responsibility over a specific program area associated with 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d920e312708190b4aede2e21f5f697 |
completed | April 10, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69d91c3d669c81908eea7ad61122d275 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.