Triple
T8816775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALPN |
E209795
|
entity |
| Predicate | roleInHTTP2 |
P57746
|
FINISHED |
| Object | selects HTTP/2 vs HTTP/1.1 over TLS |
—
|
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: selects HTTP/2 vs HTTP/1.1 over TLS | Statement: [ALPN, roleInHTTP2, selects HTTP/2 vs HTTP/1.1 over TLS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInHTTP2 Context triple: [ALPN, roleInHTTP2, selects HTTP/2 vs HTTP/1.1 over TLS]
-
A.
roleInProtocolStack
chosen
Indicates the specific function or position an entity occupies within a layered communication or protocol stack.
-
B.
roleInIntegration
Indicates the specific function or responsibility an entity has within a combined or coordinated system, process, or integration.
-
C.
roleInOperation
Indicates that an entity holds a specific function, duty, or position within a particular operation or activity.
-
D.
servesRole
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
E.
roleInAH64
Indicates that an entity has a specific functional role or position in relation to the AH-64 attack helicopter.
- 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.