Triple
T8816663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apache HTTP Server |
E209792
|
entity |
| Predicate | protocolExtensionSupport |
P35980
|
FINISHED |
| Object | SPDY via optional module |
—
|
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: SPDY via optional module | Statement: [Apache HTTP Server, protocolExtensionSupport, SPDY via optional module]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protocolExtensionSupport Context triple: [Apache HTTP Server, protocolExtensionSupport, SPDY via optional module]
-
A.
specifiesProtocolExtensionFor
Indicates that one protocol extension defines or constrains the behavior, capabilities, or usage of another protocol.
-
B.
supportedProtocol
chosen
Indicates that one entity is compatible with, implements, or can operate using a specified communication or interaction protocol.
-
C.
supportsExtensionsFrom
Indicates that one entity is capable of recognizing, loading, or interoperating with extensions originating from another entity.
-
D.
definesExtension
Indicates that one entity specifies or establishes the extension, scope, or detailed form of another entity.
-
E.
extensionMechanism
Indicates that one entity provides a way to extend, customize, or add new functionality or components to 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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc600bd8a88190ad891a96201d796b |
completed | April 1, 2026, midnight |
| PD | Predicate disambiguation | batch_69cc5c21e64c81908490e3b0875dc0d6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:46 p.m.