Triple
T7977076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6750 |
E185472
|
entity |
| Predicate | authenticationScheme |
P18412
|
FINISHED |
| Object | Bearer |
—
|
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: Bearer | Statement: [RFC 6750, authenticationScheme, Bearer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authenticationScheme Context triple: [RFC 6750, authenticationScheme, Bearer]
-
A.
authenticationType
chosen
Indicates the method or mechanism used to verify and confirm an entity’s identity in an interaction or system.
-
B.
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.
-
C.
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.
-
D.
authenticationStructure
Indicates the structural or organizational relationship between an authentication mechanism and the components or processes that implement or support it.
-
E.
authenticationSystem
Indicates that an entity functions as or is associated with a system responsible for verifying identities and controlling access.
- 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_69ca829851908190b4e03829353ee7c3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3bf716508190b4245bd5d89ae8c4 |
completed | March 31, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69cb047a8e4c81909b79e0f0bf56440c |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:14 p.m.