Triple
T36254734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Riband |
E891901
|
entity |
| Predicate | typicalPorts |
—
|
GENERATED |
| Object | New York |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPorts Context triple: [Blue Riband, typicalPorts, New York]
-
A.
typicalPort
chosen
Indicates that a specified port is commonly or normally used for a given service, protocol, or application.
-
B.
typicalStartPort
Indicates the usual or default port number on which a given service, protocol, or application is expected to start or listen.
-
C.
portAlsoKnownAs
Indicates that a port is referred to by an alternative name or alias.
-
D.
portTypes
Indicates that two entities are associated through specific types of ports or interfaces used for connection or communication.
-
E.
hasPorts
Indicates that an entity is equipped with or provides access points (ports) for connection, communication, or interface with other entities or systems.
- F. None of above.
Provenance (1 batch)
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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.