Triple
T8816777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALPN |
E209795
|
entity |
| Predicate | negotiationModel |
P9608
|
FINISHED |
| Object | client proposes list of protocols |
—
|
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: client proposes list of protocols | Statement: [ALPN, negotiationModel, client proposes list of protocols]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: negotiationModel Context triple: [ALPN, negotiationModel, client proposes list of protocols]
-
A.
negotiationMechanism
Indicates a process or method through which parties communicate and bargain to reach a mutually acceptable agreement.
-
B.
negotiation
Indicates a process in which two or more parties communicate and make offers and counteroffers to reach a mutually acceptable agreement.
-
C.
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).
-
D.
typeOfNegotiation
chosen
Indicates the specific kind or category of negotiation process that characterizes the interaction between the involved parties.
-
E.
negotiationPhase
Indicates the specific stage or step currently reached within an ongoing negotiation process between parties.
- 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.