Triple
T270948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTTP/3 |
E5630
|
entity |
| Predicate | negotiatedVia |
P9938
|
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: [HTTP/3, negotiatedVia, ALPN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: negotiatedVia Context triple: [HTTP/3, negotiatedVia, ALPN]
-
A.
negotiationAssociatedWith
Indicates a relationship where a negotiation is connected to, involves, or is conducted by a particular entity (such as a person, organization, or group).
-
B.
negotiatingParty
Indicates that an entity is actively involved as a participant in a negotiation process with another entity.
-
C.
negotiation
Indicates a process in which two or more parties communicate and make offers and counteroffers to reach a mutually acceptable agreement.
-
D.
negotiationRound
Indicates a specific stage or iteration within an ongoing negotiation process between parties.
-
E.
acquisitionType
Indicates the specific kind or category of acquisition relationship that exists between entities (such as a company buying another company, assets, or a controlling stake).
- 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_69a25853594c8190b05ec3a586ec88bf |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25e69a9248190b9e7959b43223baa |
completed | Feb. 28, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69a25b721180819080d43c43fcbccf87 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25e68f0408190bfc851c32d6eebf3 |
completed | Feb. 28, 2026, 3:18 a.m. |
Created at: Feb. 28, 2026, 2:57 a.m.