Triple
T32708662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HttpAuthenticationMechanism API |
E836339
|
entity |
| Predicate | annotationBasedConfiguration |
P62175
|
FINISHED |
| Object | @AutoApplySession |
—
|
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: @AutoApplySession | Statement: [HttpAuthenticationMechanism API, annotationBasedConfiguration, @AutoApplySession]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: annotationBasedConfiguration Context triple: [HttpAuthenticationMechanism API, annotationBasedConfiguration, @AutoApplySession]
-
A.
configurationClass
Indicates that one entity serves as the configuration class (i.e., a class defining configuration settings or parameters) for another entity.
-
B.
supportsAutoConfiguration
Indicates that one entity provides or enables automatic configuration capabilities for another entity or process.
-
C.
configurationVia
Indicates that one entity is set up, customized, or controlled through another entity serving as its configuration mechanism or source.
-
D.
notatedWith
Indicates that something is represented, marked, or written using a particular system of notation or symbols.
-
E.
annotatedBy
chosen
Indicates that one entity has been marked up, commented on, or otherwise supplied with annotations by 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c87bf9c481908804bd231d60cd30 |
completed | May 3, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:10 a.m.