Triple
T21191659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IPsec over TCP |
E522224
|
entity |
| Predicate | encapsulationDirection |
P143229
|
FINISHED |
| Object | IPsec inside TCP |
—
|
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: IPsec inside TCP | Statement: [IPsec over TCP, encapsulationDirection, IPsec inside TCP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encapsulationDirection Context triple: [IPsec over TCP, encapsulationDirection, IPsec inside TCP]
-
A.
transmissionDirection
Indicates the direction in which something is transmitted or passed from one entity to another.
-
B.
connectionDirection
Indicates the directional flow or orientation of a connection from one entity to another.
-
C.
encryptionDirection
Indicates the direction in which data is being encrypted, specifying whether it is going from source to destination or vice versa.
-
D.
packetDirection
Indicates the direction in which a data packet is traveling between network endpoints (e.g., inbound or outbound).
-
E.
encapsulation
Indicates that one entity encloses, contains, or wraps another entity or set of details within a defined boundary, often hiding internal structure from external access.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e733381f288190b3da795f62a39568 |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:07 p.m.