Triple
T38295120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US East Coast–Caribbean route |
E1022466
|
entity |
| Predicate | majorPortOnRoute |
P202041
|
FINISHED |
| Object | Port of New York and New Jersey |
E844
|
NE 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 of New York and New Jersey | Statement: [US East Coast–Caribbean route, majorPortOnRoute, Port of New York and New Jersey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorPortOnRoute Context triple: [US East Coast–Caribbean route, majorPortOnRoute, Port of New York and New Jersey]
-
A.
majorRouteTo
Indicates that one location serves as a primary or significant route or pathway leading to another location.
-
B.
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).
-
C.
hasMajorPort
Indicates that a location possesses a primary, significant seaport used for major commercial or transportation activities.
-
D.
majorPortOnRiver
Indicates that a port is a primary or significant harbor facility located on the banks of a specified river.
-
E.
onMajorRouteBetween
Indicates that one location lies along a primary or major route connecting two other locations.
- F. None of above. chosen
Provenance (5 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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0048697bd081909073640666ca6a96 |
completed | May 10, 2026, 8:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a419e01adc081908f43d31feae9c1f5 |
completed | June 28, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_6a0047bf3c248190a9ac97a7afdfe2cb |
completed | May 10, 2026, 8:54 a.m. |
| PDg | Predicate description generation | batch_6a004868cf308190a2a93c32c92f22d9 |
completed | May 10, 2026, 8:57 a.m. |
Created at: May 3, 2026, 4:30 p.m.