Triple
T29873877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mod_http2 |
E758665
|
entity |
| Predicate | negotiatesProtocolUsing |
P167696
|
FINISHED |
| Object | ALPN |
—
|
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: ALPN | Statement: [mod_http2, negotiatesProtocolUsing, ALPN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: negotiatesProtocolUsing Context triple: [mod_http2, negotiatesProtocolUsing, ALPN]
-
A.
protocolUse
Indicates that an entity employs or relies on a specific protocol to perform a communication, interaction, or operation.
-
B.
negotiatesOver
Indicates that one entity engages in discussion or bargaining with another entity concerning the terms, conditions, or details of a specific subject or item.
-
C.
protocolDiscussed
Indicates that a protocol has been reviewed and talked through between relevant parties.
-
D.
specifiesProtocol
Indicates that one entity defines or designates the communication or interaction protocol to be used by another entity.
-
E.
negotiatesBetween
Indicates a relationship where an entity acts as an intermediary to facilitate negotiation or mediation between two other entities.
- F. None of above. chosen
Provenance (4 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_69f676c8ab448190900f6f8984e105a2 |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66bd123108190b451eb6e23842adb |
completed | May 2, 2026, 9:25 p.m. |
Created at: April 29, 2026, 5:54 p.m.