Triple
T29010867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line Printer Daemon protocol |
E736561
|
entity |
| Predicate | usesPortDirection |
P11580
|
FINISHED |
| Object | server listens on TCP port 515 |
—
|
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: server listens on TCP port 515 | Statement: [Line Printer Daemon protocol, usesPortDirection, server listens on TCP port 515]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPortDirection Context triple: [Line Printer Daemon protocol, usesPortDirection, server listens on TCP port 515]
-
A.
usedOnPort
chosen
Indicates that something is applied, connected, or operates specifically on a given port.
-
B.
usedInPort
Indicates that something is utilized or operates within a specific port.
-
C.
hasPortUse
Indicates that one entity utilizes or is assigned to a particular port for access, communication, or operation.
-
D.
isPortFor
Indicates that one entity serves as a port, interface, or connection point for another entity.
-
E.
isInPort
Indicates that an entity (such as a vessel or vehicle) is currently located within or docked at a specific port.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 28, 2026, 9:42 a.m.