Triple
T21191675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IPsec over TCP |
E522224
|
entity |
| Predicate | isTransport |
P143230
|
FINISHED |
| Object | reliable byte-stream for IPsec packets |
—
|
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: reliable byte-stream for IPsec packets | Statement: [IPsec over TCP, isTransport, reliable byte-stream for IPsec packets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTransport Context triple: [IPsec over TCP, isTransport, reliable byte-stream for IPsec packets]
-
A.
usesTransport
Indicates that an entity employs or relies on a particular mode or means of transportation to move from one place to another.
-
B.
isTransportationType
Indicates that one entity functions as a mode or category of transportation for the other entity.
-
C.
transports
Indicates that one entity carries or conveys another entity from one place to another.
-
D.
transportInterface
Indicates a relationship where one entity serves as the medium or mechanism through which another entity is transported or conveyed.
-
E.
hasTransportCategory
Indicates that one entity is classified under a particular category or type of transport associated with another entity.
- 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.