Triple
T36388418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFQ Level 5 |
E896261
|
entity |
| Predicate | frameworkLevelNumber |
P99406
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [NFQ Level 5, frameworkLevelNumber, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frameworkLevelNumber Context triple: [NFQ Level 5, frameworkLevelNumber, 5]
-
A.
frameworkLevel
Indicates the hierarchical or maturity level assigned to a particular framework within a defined system or context.
-
B.
frameworkLayer
Indicates a relationship where one framework is organized within, built upon, or conceptually assigned to a particular architectural or conceptual layer.
-
C.
architectureLevel
Indicates the relative layer or tier an entity occupies within an architectural structure or system design.
-
D.
configurationLevel
Indicates the degree or tier of settings or parameters applied to configure something within a system or context.
-
E.
hasLevelNumber
chosen
Indicates that an entity is associated with a specific level identified by a numerical value.
- 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.