Triple
T9930930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Point-to-Point Encryption Standard |
E192645
|
entity |
| Predicate | encryptionStartPoint |
P389
|
FINISHED |
| Object | point of capture |
—
|
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: point of capture | Statement: [Point-to-Point Encryption Standard, encryptionStartPoint, point of capture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encryptionStartPoint Context triple: [Point-to-Point Encryption Standard, encryptionStartPoint, point of capture]
-
A.
encryptionDirection
Indicates the direction in which data is being encrypted, specifying whether it is going from source to destination or vice versa.
-
B.
cryptLocation
Indicates the specific place or structure where a crypt is situated or housed.
-
C.
startPoint
chosen
Indicates the initial location or position from which an object, path, or action begins.
-
D.
cryptUse
Indicates that one entity uses, applies, or relies on a cryptographic method, key, or mechanism in relation to another entity or data.
-
E.
encryptionLevel
Indicates the degree or strength of cryptographic protection applied to data or communications.
- 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5b4196881909a004091a4203c45 |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:43 p.m.