Triple
T18175709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YEADE |
E435150
|
entity |
| Predicate | associatedPortFunction |
P17285
|
FINISHED |
| Object | port |
—
|
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: port | Statement: [YEADE, associatedPortFunction, port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedPortFunction Context triple: [YEADE, associatedPortFunction, port]
-
A.
associatedFunction
Indicates that one entity has a related or linked function that is conceptually or operationally connected to it.
-
B.
portFunction
chosen
Indicates the specific operational role or purpose that a port serves within a system or network.
-
C.
connectionPort
Indicates a specific port through which two components, systems, or devices are connected or can communicate.
-
D.
registeredPort
Indicates that a specific network port number has been officially assigned and recorded for use by a particular service or protocol.
-
E.
linkedToPort
Indicates that one entity is connected or associated with a specific port, such as a network, hardware, or interface 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4df59bf3881909adc28cacbe9cb39 |
completed | April 19, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.