Triple
T21191653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IPsec over TCP |
E522224
|
entity |
| Predicate | canUsePort |
P56804
|
FINISHED |
| Object | custom TCP port |
—
|
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: custom TCP port | Statement: [IPsec over TCP, canUsePort, custom TCP port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canUsePort Context triple: [IPsec over TCP, canUsePort, custom TCP port]
-
A.
usedPort
Indicates that a particular port (such as a network or hardware interface) is or has been utilized by an entity for communication or connection.
-
B.
usedOnPort
Indicates that something is applied, connected, or operates specifically on a given port.
-
C.
isPortFor
Indicates that one entity serves as a port, interface, or connection point for another entity.
-
D.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
E.
hasPortCapability
chosen
Indicates that an entity possesses the ability or feature to support, provide, or utilize a specific type of port or port-related function.
- 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_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. |
Created at: April 16, 2026, 3:07 p.m.