Triple
T32583649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 863 |
E832857
|
entity |
| Predicate | IANAWellKnownPort |
P3689
|
FINISHED |
| Object | 9 |
—
|
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: 9 | Statement: [RFC 863, IANAWellKnownPort, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IANAWellKnownPort Context triple: [RFC 863, IANAWellKnownPort, 9]
-
A.
wellKnownPortRange
chosen
Indicates that a port number falls within the standardized range of well-known ports (typically 0–1023) reserved for common network services.
-
B.
typicalPort
Indicates that a specified port is commonly or normally used for a given service, protocol, or application.
-
C.
portAlsoKnownAs
Indicates that a port is referred to by an alternative name or alias.
-
D.
registeredWithIANA
Indicates that an entity is officially recorded and recognized by the Internet Assigned Numbers Authority (IANA) in its registries.
-
E.
portNumber
Indicates the specific communication port assigned to a network connection, service, or endpoint.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c66c41b481908abc65d5d284bcee |
completed | May 3, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:04 a.m.