Triple
T12207328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITIL |
E290868
|
entity |
| Predicate | hasVersion |
P455
|
FINISHED |
| Object | ITIL v3 |
E290868
|
NE 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: ITIL v3 | Statement: [ITIL, hasVersion, ITIL v3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ITIL v3 Context triple: [ITIL, hasVersion, ITIL v3]
-
A.
ITIL
chosen
ITIL is a widely adopted framework of best practices for IT service management that helps organizations align their IT services with business needs.
-
B.
Itil
Itil was the medieval capital city of the Khazar Khaganate, strategically located near the Caspian Sea as a major commercial and political center.
-
C.
ISO/IEC 20000
ISO/IEC 20000 is an international standard that specifies requirements for establishing, implementing, maintaining, and continually improving an IT service management system.
-
D.
ISO/IEC 20000-3
ISO/IEC 20000-3 is a supporting part of the ISO/IEC 20000 IT service management standard that provides guidance on defining the scope and applicability of an IT service management system.
-
E.
IT4IT Reference Architecture
The IT4IT Reference Architecture is a standardized framework that defines an end-to-end, value chain–oriented approach for managing the business of IT.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d91c7d8f5c8190a46e9caa2a920fa9 |
completed | April 10, 2026, 3:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f60a9ae3d48190a220ccd37ce8d3e7 |
completed | May 2, 2026, 2:30 p.m. |
Created at: April 8, 2026, 9:51 p.m.