Triple
T10926966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Client Certificate URL extension |
E258093
|
entity |
| Predicate | extensionType |
P96689
|
FINISHED |
| Object | TLS hello extension |
—
|
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: TLS hello extension | Statement: [Client Certificate URL extension, extensionType, TLS hello extension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extensionType Context triple: [Client Certificate URL extension, extensionType, TLS hello extension]
-
A.
extension
Indicates that one entity is a lengthening, continuation, or added part of another entity beyond its original limits.
-
B.
extensionTerminus
Indicates the endpoint or final limit to which something is extended or continues.
-
C.
extensionMechanism
Indicates that one entity provides a way to extend, customize, or add new functionality or components to another entity.
-
D.
definesExtension
Indicates that one entity specifies or establishes the extension, scope, or detailed form of another entity.
-
E.
extensionPotential
Indicates the potential or likelihood that an existing arrangement, contract, or state will be extended beyond its current term or scope.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7709165188190aa30dd08deddade4 |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d72e799f808190b6ab64fc7586a303 |
completed | April 9, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69d7322370648190ba14cdd6fb4cdcb0 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:22 p.m.