Triple
T36553600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSH KEXINIT message |
E901637
|
entity |
| Predicate | hasCookieLength |
P204931
|
FINISHED |
| Object | 16 bytes |
—
|
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: 16 bytes | Statement: [SSH KEXINIT message, hasCookieLength, 16 bytes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCookieLength Context triple: [SSH KEXINIT message, hasCookieLength, 16 bytes]
-
A.
defaultMaxCookieSize
Indicates the maximum allowed size for a cookie when no specific limit has been explicitly set.
-
B.
hasMaximumAgeInGa
Indicates that an entity has an upper age limit, measured in billions of years (giga-annum, Ga).
-
C.
hasAccessLength
Indicates that an entity is associated with a specific measure or duration of access.
-
D.
cookieType
Indicates the specific kind or category of cookie associated with an entity.
-
E.
usesMagicCookie
Indicates that one entity employs a special, often opaque identifier or token (“magic cookie”) to recognize, authenticate, or manage its interaction with another entity or system.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:11 p.m.