Triple
T9865351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 977 |
E239817
|
entity |
| Predicate | portUsage |
P11580
|
FINISHED |
| Object | uses well-known TCP port 119 by default |
—
|
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: uses well-known TCP port 119 by default | Statement: [RFC 977, portUsage, uses well-known TCP port 119 by default]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portUsage Context triple: [RFC 977, portUsage, uses well-known TCP port 119 by default]
-
A.
portActivity
Indicates the level or type of operational activity occurring at a port, such as ship movements, cargo handling, or related maritime operations.
-
B.
portConfiguration
Indicates how ports are arranged, assigned, or set up for use within a system or device.
-
C.
portLocation
Indicates that a port is geographically situated at or associated with a specific location.
-
D.
port
Indicates a relationship where one entity serves as a harbor, access point, or interface through which another entity can enter, exit, or connect.
-
E.
usedOnPort
chosen
Indicates that something is applied, connected, or operates specifically on a given 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_69ca84e7506c819095cbde4ff16512bb |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3ba7f288190a15ebec2cc3112c4 |
completed | April 2, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69cd1d7621d48190aa6a6f34399514b0 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:36 p.m.