Triple
T38220707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunpowder River watershed |
E1012000
|
entity |
| Predicate | lowerRegion |
P112192
|
FINISHED |
| Object | Atlantic Coastal Plain |
—
|
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: Atlantic Coastal Plain | Statement: [Gunpowder River watershed, lowerRegion, Atlantic Coastal Plain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerRegion Context triple: [Gunpowder River watershed, lowerRegion, Atlantic Coastal Plain]
-
A.
lowerLocation
Indicates that one entity is located physically below or at a lower vertical position relative to another entity.
-
B.
lowerField
Indicates that one field or attribute has a lower (e.g., smaller, lesser, or inferior) value or position relative to another field.
-
C.
lowerBoundaryLocation
Indicates the place or region where the lower or bottom boundary of something is situated.
-
D.
lowestZone
Indicates that one entity occupies or corresponds to the lowest-ranked or lowest-level zone among a set of zones.
-
E.
lowerGSSPLocation
chosen
Indicates that one location is geographically or spatially situated below another specified 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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.