Triple
T2114503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FTP |
E42574
|
entity |
| Predicate | dataChannelPortType |
P21260
|
FINISHED |
| Object | ephemeral port (in passive mode) |
—
|
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: ephemeral port (in passive mode) | Statement: [FTP, dataChannelPortType, ephemeral port (in passive mode)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataChannelPortType Context triple: [FTP, dataChannelPortType, ephemeral port (in passive mode)]
-
A.
dataPortal
Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
-
B.
virtualChannel
Indicates that one entity is linked to another through a non-physical, software-defined communication channel used for transmitting data or signals.
-
C.
dataBusType
Indicates the type or category of data bus used to transfer data between components or systems.
-
D.
controlledPort
Indicates that one entity has authority over or manages the operation or configuration of a specific port of another entity.
-
E.
portConfiguration
chosen
Indicates how ports are arranged, assigned, or set up for use within a system or device.
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb05b51c81908a78c816f492c45c |
completed | March 7, 2026, 5:43 a.m. |
| PD | Predicate disambiguation | batch_69abb7ba08948190a3c236bb53ee4257 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.