Triple
T8470964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Filing Protocol |
E200278
|
entity |
| Predicate | networkPort |
P2548
|
FINISHED |
| Object | TCP port 548 |
—
|
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: TCP port 548 | Statement: [Apple Filing Protocol, networkPort, TCP port 548]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkPort Context triple: [Apple Filing Protocol, networkPort, TCP port 548]
-
A.
portNumber
chosen
Indicates the specific communication port assigned to a network connection, service, or endpoint.
-
B.
connectionPort
Indicates a specific port through which two components, systems, or devices are connected or can communicate.
-
C.
registeredPort
Indicates that a specific network port number has been officially assigned and recorded for use by a particular service or protocol.
-
D.
networkHost
Indicates that one entity serves as the host machine or node on which another networked entity (such as a service, application, or connection) resides or operates.
-
E.
typicalPort
Indicates that a specified port is commonly or normally used for a given service, protocol, or application.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f234c481909534de6fd702f4cf |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.