Triple
T772569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Wild and Scenic Rivers System units |
E16312
|
entity |
| Predicate | protectionFocus |
P8850
|
FINISHED |
| Object | river free-flowing character |
—
|
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: river free-flowing character | Statement: [National Wild and Scenic Rivers System units, protectionFocus, river free-flowing character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectionFocus Context triple: [National Wild and Scenic Rivers System units, protectionFocus, river free-flowing character]
-
A.
protects
Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
-
B.
protectionObjective
chosen
Indicates that one entity has the goal or purpose of safeguarding, defending, or preserving another entity or its interests.
-
C.
aimsToProtect
Indicates an intention or purpose to safeguard or defend one entity, value, or condition from harm, risk, or undesirable outcomes.
-
D.
protectionType
Indicates the kind or method of protection that is applied to or associated with an entity.
-
E.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
- 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a72eda6c81908205ae5a1e05cc20 |
completed | March 1, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69a4a508c42c8190850a0ac7844a3ea9 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.