Triple
T8285788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | oVirt |
E193782
|
entity |
| Predicate | supportsOpenIDConnectIntegration |
P82522
|
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: [oVirt, supportsOpenIDConnectIntegration, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsOpenIDConnectIntegration Context triple: [oVirt, supportsOpenIDConnectIntegration, yes]
-
A.
supportsSignInMethod
Indicates that one entity enables or allows another entity to use a particular sign-in or authentication method.
-
B.
supportsAAD
Indicates that one entity provides compatibility with or operational backing for Azure Active Directory (AAD) for another entity.
-
C.
supportsThirdPartyApplications
Indicates that an entity is capable of working with, integrating, or allowing the use of software applications developed by external third parties.
-
D.
supportsConditionalAccess
Indicates that one entity enables or is compatible with applying conditional access controls or policies to another entity or interaction.
-
E.
supportsProvisioningMethod
Indicates that one entity is capable of using or is compatible with a particular provisioning method offered or required by another entity.
- F. None of above. chosen
Provenance (4 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7ad20ae481908179aba245c73fad |
completed | March 31, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69cb70ad9fc081908741f8c4a4141edf |
completed | March 31, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:52 p.m.