Triple
T36553566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PPP over Secure Shell (SSH) |
E901636
|
entity |
| Predicate | canEncapsulate |
P128017
|
FINISHED |
| Object | IPv4 |
—
|
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: IPv4 | Statement: [PPP over Secure Shell (SSH), canEncapsulate, IPv4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canEncapsulate Context triple: [PPP over Secure Shell (SSH), canEncapsulate, IPv4]
-
A.
canWrap
chosen
Indicates that one entity is able to enclose, cover, or surround another entity, typically forming an outer layer or container around it.
-
B.
encapsulatesProtocol
Indicates that one entity implements and contains the functionality of a specific communication or interaction protocol on behalf of another entity.
-
C.
canExpress
Indicates that an entity has the ability or capacity to convey, articulate, or communicate something (such as an idea, emotion, or property).
-
D.
canHold
Indicates that one entity has the capacity or ability to contain, support, or carry another entity.
-
E.
encapsulationDirection
Indicates the direction in which one entity encloses, contains, or wraps around another within an encapsulation relationship.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.