Triple
T30525819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lower Pahranagat Lake |
E776837
|
entity |
| Predicate | hasPrimaryWildlifeGroup |
P153364
|
FINISHED |
| Object | migratory waterfowl |
—
|
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: migratory waterfowl | Statement: [Lower Pahranagat Lake, hasPrimaryWildlifeGroup, migratory waterfowl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryWildlifeGroup Context triple: [Lower Pahranagat Lake, hasPrimaryWildlifeGroup, migratory waterfowl]
-
A.
hasWildlifeCharacteristic
Indicates that an entity possesses a particular trait, feature, or quality related to wildlife.
-
B.
hasWildlifeStatus
Indicates the conservation or protection status assigned to wildlife associated with an entity.
-
C.
hasMajorWildlife
chosen
Indicates that a location or area supports significant populations or habitats of important wildlife species.
-
D.
hasWildlifeSite
Indicates that a location or entity possesses, contains, or is designated as a wildlife site.
-
E.
hasWildlifeRegion
Indicates that an entity is associated with or located within a designated wildlife region or habitat area.
- 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fff09dae088190bd8460060d778feb |
completed | May 10, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_69fff0027c5c8190baa5c7a15852cbe0 |
completed | May 10, 2026, 2:40 a.m. |
Created at: April 29, 2026, 8:17 p.m.