Triple
T4832116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MediaWiki |
E107967
|
entity |
| Predicate | supportsLDAP |
P47053
|
FINISHED |
| Object | LDAP authentication via extensions |
—
|
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: LDAP authentication via extensions | Statement: [MediaWiki, supportsLDAP, LDAP authentication via extensions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLDAP Context triple: [MediaWiki, supportsLDAP, LDAP authentication via extensions]
-
A.
supportedDirectoryService
chosen
Indicates that a system, application, or component is compatible with and can operate using a particular directory service.
-
B.
supportsAAD
Indicates that one entity provides compatibility with or operational backing for Azure Active Directory (AAD) for another entity.
-
C.
supportsSignInMethod
Indicates that one entity enables or allows another entity to use a particular sign-in or authentication method.
-
D.
supportsMultiuser
Indicates that the subject is capable of handling or enabling simultaneous use by multiple users.
-
E.
supportsConditionalAccess
Indicates that one entity enables or is compatible with applying conditional access controls or policies to another entity or interaction.
- 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_69bd43fac8188190803f0327190621e4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c21c7f08190846049d31fdfa144 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:24 p.m.