Triple
T7937861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Hat Ansible Certified Content |
E184326
|
entity |
| Predicate | supportLevel |
P936
|
FINISHED |
| Object | enterprise support |
—
|
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: enterprise support | Statement: [Red Hat Ansible Certified Content, supportLevel, enterprise support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportLevel Context triple: [Red Hat Ansible Certified Content, supportLevel, enterprise support]
-
A.
publicSupportLevel
Indicates the degree or intensity of approval, endorsement, or backing that the general public gives to a particular entity, action, or proposal.
-
B.
serviceLevel
Indicates the degree or quality of service provided or received in the relationship between entities.
-
C.
typeOfSupport
chosen
Indicates the kind or category of assistance, help, or backing provided in a given context.
-
D.
support
Indicates that one entity provides assistance, endorsement, or backing to another entity or its actions.
-
E.
sponsorLevel
Indicates the degree or tier of sponsorship that one entity provides to another.
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3aef2394819086eea1f6ab117aed |
completed | March 31, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69cae93526d081909303265bf60419fd |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:08 p.m.