Triple
T8285785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | oVirt |
E193782
|
entity |
| Predicate | supportsExternalAuthentication |
P40818
|
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, supportsExternalAuthentication, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsExternalAuthentication Context triple: [oVirt, supportsExternalAuthentication, yes]
-
A.
supportsSignInMethod
chosen
Indicates that one entity enables or allows another entity to use a particular sign-in or authentication method.
-
B.
supportsRepositoryAuthentication
Indicates that an entity provides or enables authentication mechanisms for accessing a repository.
-
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.
authenticationStandard
Indicates that one entity defines, specifies, or adheres to a particular method, protocol, or set of rules for verifying the identity of another entity.
-
E.
supportsMultiuser
Indicates that the subject is capable of handling or enabling simultaneous use by multiple users.
- 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.