Triple
T25287792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chattooga River |
E633991
|
entity |
| Predicate | designatedAsWildAndScenic |
P82588
|
FINISHED |
| Object | 1974 |
—
|
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: 1974 | Statement: [Chattooga River, designatedAsWildAndScenic, 1974]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designatedAsWildAndScenic Context triple: [Chattooga River, designatedAsWildAndScenic, 1974]
-
A.
hasWildAndScenicDesignation
chosen
Indicates that an area or waterway has been formally designated under a Wild and Scenic protection status.
-
B.
designatedWilderness
Indicates that an area has been officially classified and protected as wilderness under a formal designation or legal framework.
-
C.
designatedAsNationalPark
Indicates that an area has been officially assigned the legal status and protections of a national park by an authorized governing body.
-
D.
stateScenicRiverDesignation
Indicates that a river or river segment has been officially designated by a state as part of its scenic river system or program.
-
E.
designatedAsWildlifeRefuge
Indicates that an area has been officially assigned the status and protections of a wildlife refuge.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 21, 2026, 1:19 p.m.