Triple
T26129346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overfalls Shoal lightship station |
E659192
|
entity |
| Predicate | nearbyPortsServed |
P174660
|
FINISHED |
| Object | Port of Philadelphia |
—
|
NE NERFINISHED |
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 Philadelphia | Statement: [Overfalls Shoal lightship station, nearbyPortsServed, Port of Philadelphia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyPortsServed Context triple: [Overfalls Shoal lightship station, nearbyPortsServed, Port of Philadelphia]
-
A.
nearbyCityServed
Indicates that a city is geographically close enough to another city to be considered within its service or support area.
-
B.
nearbyPortFacility
Indicates that one entity is located close to or in the immediate vicinity of a port facility.
-
C.
nearbyCityOrPort
Indicates that one location is geographically close to a city or port, typically within a short travel distance.
-
D.
servedPorts
Indicates that a network service or device makes specific ports available to accept incoming connections or traffic.
-
E.
servedNearbyEstates
Indicates that an entity provided services or assistance to estates located in its immediate geographic vicinity.
- F. None of above. chosen
Provenance (4 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_69ee5bc2b2948190b458ad3f580af779 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6c5b7e46081909975b05f7298cc0e |
completed | May 3, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c49069e48190a3486b6254a6645b |
completed | May 3, 2026, 3:44 a.m. |
Created at: April 26, 2026, 8:13 p.m.