Triple
T33027451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PASV |
E845079
|
entity |
| Predicate | dataPortOpenedBy |
P175707
|
FINISHED |
| Object | FTP server |
—
|
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: FTP server | Statement: [PASV, dataPortOpenedBy, FTP server]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataPortOpenedBy Context triple: [PASV, dataPortOpenedBy, FTP server]
-
A.
openedPort
Indicates that a network port on a host or device is currently open and able to accept incoming connections.
-
B.
openedPorts
Indicates that a network host has specific communication ports currently open and available for connections.
-
C.
openedPorts
Indicates that certain network ports on a host or device are currently open and accepting connections.
-
D.
hasPortOn
Indicates that one entity possesses or is located adjacent to a port situated on another specified geographic or infrastructural feature (such as a coast, river, or lake).
-
E.
connectionPort
Indicates a specific port through which two components, systems, or devices are connected or can communicate.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: May 1, 2026, 1:23 a.m.