Triple
T21194146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Groom Dry Lake |
E522282
|
entity |
| Predicate | mapVisibility |
P143505
|
FINISHED |
| Object | partially obscured on some historical maps |
—
|
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: partially obscured on some historical maps | Statement: [Groom Dry Lake, mapVisibility, partially obscured on some historical maps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapVisibility Context triple: [Groom Dry Lake, mapVisibility, partially obscured on some historical maps]
-
A.
mapDisplay
Indicates that something is being visually represented or shown on a map interface.
-
B.
mapsType
Indicates that one entity serves as a mapping whose values or outputs are of the specified type.
-
C.
mapUse
Indicates a relationship where one entity uses, applies, or employs a map (or mapping) to perform an action or achieve a purpose.
-
D.
mapsIncluded
Indicates that one map or mapping is contained within, or is a subset of, another map or mapping.
-
E.
mapsFocus
Indicates that one entity serves as the primary subject, area, or aspect of attention, emphasis, or concentration for another entity.
- F. None of above. chosen
Provenance (4 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73339aaa081909d9009c58c386422 |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5fa92a2448190896c022dd27511ad |
completed | April 20, 2026, 10:06 a.m. |
Created at: April 16, 2026, 3:08 p.m.