Triple
T13208126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Trieste |
E314418
|
entity |
| Predicate | freePortStatusSince |
P108509
|
FINISHED |
| Object | 1719 |
—
|
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: 1719 | Statement: [Port of Trieste, freePortStatusSince, 1719]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: freePortStatusSince Context triple: [Port of Trieste, freePortStatusSince, 1719]
-
A.
openedPort
Indicates that a network port on a host or device is currently open and able to accept incoming connections.
-
B.
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.
-
C.
registeredPort
Indicates that a specific network port number has been officially assigned and recorded for use by a particular service or protocol.
-
D.
hasPortStatus
Indicates the current operational or connectivity state of a specific port in a system or device.
-
E.
dynamicPortRange
Indicates that a system or service uses a configurable range of network ports that can be dynamically allocated rather than fixed to a single port.
- 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c9cb7ac819095cff8699993c419 |
completed | April 10, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98c959ba08190adf29dc0c4e1fca6 |
completed | April 10, 2026, 11:49 p.m. |
Created at: April 9, 2026, 9:17 p.m.