Triple
T8285787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | oVirt |
E193782
|
entity |
| Predicate | supportsActiveDirectoryIntegration |
P47053
|
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, supportsActiveDirectoryIntegration, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsActiveDirectoryIntegration Context triple: [oVirt, supportsActiveDirectoryIntegration, yes]
-
A.
supportsAAD
Indicates that one entity provides compatibility with or operational backing for Azure Active Directory (AAD) for another entity.
-
B.
hasCentralAdministrationIn
Indicates that an organization or entity maintains its primary central administrative authority or headquarters in a specified location.
-
C.
supportsConditionalAccess
Indicates that one entity enables or is compatible with applying conditional access controls or policies to another entity or interaction.
-
D.
supportedDirectoryService
chosen
Indicates that a system, application, or component is compatible with and can operate using a particular directory service.
-
E.
isAdministrativeUnit
Indicates that one entity functions as an official administrative division or unit within the governance or organizational structure of 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_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. |
Created at: March 30, 2026, 5:52 p.m.