Triple
T30503466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maher Terminals |
E776200
|
entity |
| Predicate | hasRoleInPort |
P130959
|
FINISHED |
| Object | container terminal operator at Port of New York and New Jersey |
—
|
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: container terminal operator at Port of New York and New Jersey | Statement: [Maher Terminals, hasRoleInPort, container terminal operator at Port of New York and New Jersey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleInPort Context triple: [Maher Terminals, hasRoleInPort, container terminal operator at Port of New York and New Jersey]
-
A.
hasPortRole
chosen
Indicates that an entity participates in a port with a specified functional or operational role.
-
B.
isInPort
Indicates that an entity (such as a vessel or vehicle) is currently located within or docked at a specific port.
-
C.
hasRole
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
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.
hasNearbyPortAccess
Indicates that an entity is located close enough to a port to feasibly use it for access or transport.
- 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 29, 2026, 8:15 p.m.