Triple
T12703992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Bonneville |
E303531
|
entity |
| Predicate | modernRemnantType |
P57740
|
FINISHED |
| Object | saline lake (Great Salt Lake) |
—
|
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: saline lake (Great Salt Lake) | Statement: [Lake Bonneville, modernRemnantType, saline lake (Great Salt Lake)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernRemnantType Context triple: [Lake Bonneville, modernRemnantType, saline lake (Great Salt Lake)]
-
A.
remnantType
chosen
Indicates the specific kind or category of remnant that results from or is associated with an entity or process.
-
B.
modernBase
Indicates that one entity serves as the contemporary or current foundational basis or reference point for another entity.
-
C.
modernizationType
Indicates the specific kind or category of modernization applied to an entity or system.
-
D.
highestRemnant
Indicates that one entity is the remnant with the greatest remaining value, size, or intensity relative to other comparable remnants.
-
E.
remnants
Indicates that parts or traces of something remain after the main portion has been removed, used, or destroyed.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d962a32c6481908ddaddae4ea267bf |
completed | April 10, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69d960be63f081908a5ef5ef17a311bf |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:23 p.m.