Triple
T3037903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Philadelphia |
E83054
|
entity |
| Predicate | typeOfPort |
P16380
|
FINISHED |
| Object | deep-water 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: deep-water port | Statement: [Port of Philadelphia, typeOfPort, deep-water port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPort Context triple: [Port of Philadelphia, typeOfPort, deep-water port]
-
A.
hasPortType
chosen
Indicates that an entity is associated with, or characterized by, a specific type or category of port.
-
B.
typicalPort
Indicates that a specified port is commonly or normally used for a given service, protocol, or application.
-
C.
portNumber
Indicates the specific communication port assigned to a network connection, service, or endpoint.
-
D.
hasPortOn
Indicates that one entity possesses or is located adjacent to a port situated on another specified geographic or infrastructural feature (such as a coast, river, or lake).
-
E.
portLocation
Indicates that a port is geographically situated at or associated with a specific location.
- 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_69ad8b2298908190a7cb4e9bdbf064d0 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9b2e03c88190b4e2f01f07c9303a |
completed | March 8, 2026, 3:52 p.m. |
| PD | Predicate disambiguation | batch_69ad961fc62c819087c4c3a44b00847d |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.