Triple
T5347048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RADIUS |
E124082
|
entity |
| Predicate | legacyPortAccounting |
P63162
|
FINISHED |
| Object | 1646 |
—
|
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: 1646 | Statement: [RADIUS, legacyPortAccounting, 1646]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legacyPortAccounting Context triple: [RADIUS, legacyPortAccounting, 1646]
-
A.
registeredPort
Indicates that a specific network port number has been officially assigned and recorded for use by a particular service or protocol.
-
B.
controlledPort
Indicates that one entity has authority over or manages the operation or configuration of a specific port of another entity.
-
C.
hasMaintenancePort
Indicates that an entity is equipped with a dedicated port or interface used specifically for maintenance, diagnostics, or service operations.
-
D.
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.
-
E.
registeredPortRange
Indicates that a port number falls within the officially registered (non-well-known, non-dynamic) range of port values.
- F. None of above. chosen
Provenance (4 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_69bd464be27081908807b40b75c1bbae |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85ede7c481908347d557aa4d19ad |
completed | March 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69bd845a62b081909782863865b257a9 |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd85e69e808190b29548670fd2900a |
completed | March 20, 2026, 5:37 p.m. |
Created at: March 20, 2026, 2:01 p.m.