Triple
T7928249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 868 |
E184121
|
entity |
| Predicate | udpPort |
P2548
|
FINISHED |
| Object | 37 |
—
|
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: 37 | Statement: [RFC 868, udpPort, 37]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: udpPort Context triple: [RFC 868, udpPort, 37]
-
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.
defaultPort
Indicates that one entity serves as the standard or preconfigured communication port used by another entity unless explicitly overridden.
-
E.
usedPort
Indicates that a particular port (such as a network or hardware interface) is or has been utilized by an entity for communication or connection.
- 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_69ca828fe7bc819090f52c88dcd72183 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3ac9ac4c819082cd2190fc3ce5a2 |
completed | March 31, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69cae9335f288190ba96781fd6576a2b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:07 p.m.