Triple
T32536458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun RPC |
E831601
|
entity |
| Predicate | portmapperPurpose |
P17285
|
FINISHED |
| Object | map RPC program numbers to network ports |
—
|
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: map RPC program numbers to network ports | Statement: [Sun RPC, portmapperPurpose, map RPC program numbers to network ports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portmapperPurpose Context triple: [Sun RPC, portmapperPurpose, map RPC program numbers to network ports]
-
A.
portFunction
chosen
Indicates the specific operational role or purpose that a port serves within a system or network.
-
B.
portSystem
Indicates that one system serves as a port or interface through which another system connects, communicates, or transfers data or resources.
-
C.
portNumber
Indicates the specific communication port assigned to a network connection, service, or endpoint.
-
D.
portAlsoKnownAs
Indicates that a port is referred to by an alternative name or alias.
-
E.
portConfiguration
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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c57062c481908b041788842c5990 |
completed | May 3, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:01 a.m.