Triple
T30390071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potomac River estuary |
E773052
|
entity |
| Predicate | hasProtectedAreaAlongShore |
P58633
|
FINISHED |
| Object | Piscataway Park |
—
|
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: Piscataway Park | Statement: [Potomac River estuary, hasProtectedAreaAlongShore, Piscataway Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtectedAreaAlongShore Context triple: [Potomac River estuary, hasProtectedAreaAlongShore, Piscataway Park]
-
A.
protectedAreaOnShore
chosen
Indicates that a protected area is located on or along a shoreline.
-
B.
coastTypeProtected
Indicates that a coastline is designated as protected, such as through conservation status, legal safeguards, or restricted human use.
-
C.
hasProtectedAreaOnMainIsland
Indicates that a protected area is located on the main island of a given geographic or political entity.
-
D.
hasCoastalProtectionConcern
Indicates that an entity has an issue, risk, or consideration related to protecting coastal areas from environmental or human impacts.
-
E.
hasCoastlineDesignation
Indicates that a geographic area’s coastline has been assigned a specific official classification or status.
- 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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ffe01c9d3c819084c256bb3c81c0dc |
completed | May 10, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ffdfcc78b08190aa4493f13d62a531 |
completed | May 10, 2026, 1:30 a.m. |
Created at: April 29, 2026, 8:02 p.m.