Triple
T19746965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackwater Falls |
E474275
|
entity |
| Predicate | stateParkEstablished |
P116803
|
FINISHED |
| Object | Blackwater Falls State Park established 1937 |
—
|
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: Blackwater Falls State Park established 1937 | Statement: [Blackwater Falls, stateParkEstablished, Blackwater Falls State Park established 1937]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateParkEstablished Context triple: [Blackwater Falls, stateParkEstablished, Blackwater Falls State Park established 1937]
-
A.
stateParkEstablishedFor
Indicates that a state park was created or designated for the benefit, use, or purpose of a particular entity or objective.
-
B.
stateParkDesignationYear
chosen
Indicates the year in which an area was officially designated as a state park.
-
C.
dateEstablishedAsNationalPark
Indicates the date on which a location or area was officially designated as a national park.
-
D.
stateHistoricParkDesignationYear
Indicates the year in which a place or site was officially designated as a state historic park.
-
E.
establishedAsPark
Indicates that an area or site has been officially designated and recognized as a park.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65294b4008190818eda40630f4147 |
completed | April 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:47 p.m.