Triple
T10605977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INBOM |
E275876
|
entity |
| Predicate | associatedPortType |
P16380
|
FINISHED |
| Object | seaport |
—
|
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: seaport | Statement: [INBOM, associatedPortType, seaport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedPortType Context triple: [INBOM, associatedPortType, seaport]
-
A.
connectionPort
Indicates a specific port through which two components, systems, or devices are connected or can communicate.
-
B.
linkedToPort
Indicates that one entity is connected or associated with a specific port, such as a network, hardware, or interface port.
-
C.
registeredPort
Indicates that a specific network port number has been officially assigned and recorded for use by a particular service or protocol.
-
D.
hasPortType
chosen
Indicates that an entity is associated with, or characterized by, a specific type or category of port.
-
E.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df4a5df88190b993196ca7849a88 |
completed | April 8, 2026, 11:05 p.m. |
| PD | Predicate disambiguation | batch_69d6dd72c1288190adbb5e79e94c044a |
completed | April 8, 2026, 10:57 p.m. |
Created at: April 8, 2026, 7:32 p.m.