Triple
T29873792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGINX, Inc. |
E758663
|
entity |
| Predicate | primaryProtocolSupport |
P35980
|
FINISHED |
| Object | HTTP |
—
|
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: HTTP | Statement: [NGINX, Inc., primaryProtocolSupport, HTTP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryProtocolSupport Context triple: [NGINX, Inc., primaryProtocolSupport, HTTP]
-
A.
primaryProtocol
Indicates that one protocol is designated as the main or default protocol used in a given context or interaction.
-
B.
supportedProtocol
chosen
Indicates that one entity is compatible with, implements, or can operate using a specified communication or interaction protocol.
-
C.
parentProtocol
Indicates that one protocol serves as the direct ancestor or higher-level specification from which another protocol is derived or extended.
-
D.
associatedProtocol
Indicates that one entity is linked to, governed by, or operates according to a particular protocol.
-
E.
targetsProtocol
Indicates that one entity is designed to interact with, affect, or be applied to a specific protocol.
- 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a01a23d8b148190ac2c8765aa9227c4 |
completed | May 11, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_6a01a1e8bb90819096647e929bfb3db8 |
completed | May 11, 2026, 9:31 a.m. |
Created at: April 29, 2026, 5:54 p.m.