Triple
T5479459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSPF |
E123434
|
entity |
| Predicate | authenticationMethods |
P18412
|
FINISHED |
| Object | null authentication |
—
|
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: null authentication | Statement: [OSPF, authenticationMethods, null authentication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authenticationMethods Context triple: [OSPF, authenticationMethods, null authentication]
-
A.
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.
-
B.
authenticationType
chosen
Indicates the method or mechanism used to verify and confirm an entity’s identity in an interaction or system.
-
C.
authenticationSystem
Indicates that an entity functions as or is associated with a system responsible for verifying identities and controlling access.
-
D.
supportsSignInMethod
Indicates that one entity enables or allows another entity to use a particular sign-in or authentication method.
-
E.
authenticationProtocol
Indicates that a particular method or set of rules is used to verify the identity of an entity before granting access or performing an action.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9247a16c8190ac5a02534da48853 |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.