Triple
T31472344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Okeechobee |
E802891
|
entity |
| Predicate | protectedByStructure |
P957
|
FINISHED |
| Object | Herbert Hoover Dike |
—
|
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: Herbert Hoover Dike | Statement: [Lake Okeechobee, protectedByStructure, Herbert Hoover Dike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectedByStructure Context triple: [Lake Okeechobee, protectedByStructure, Herbert Hoover Dike]
-
A.
protectedBy
chosen
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
B.
guardedStructure
Indicates that a structure is being protected or watched over by a guarding entity or mechanism.
-
C.
hasProtectedStructure
Indicates that an entity possesses or is associated with a structure that is designated as protected (e.g., legally, environmentally, or culturally safeguarded).
-
D.
protectedByAct
Indicates that something is safeguarded, regulated, or granted legal status under a specific legislative act or statute.
-
E.
protectedFor
Indicates that something is safeguarded or preserved specifically for the benefit, use, or rights of a particular entity or purpose.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 30, 2026, 9:27 p.m.