Triple
T26124124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nevada ghost towns |
E659053
|
entity |
| Predicate | mainCauseOfAbandonment |
P20519
|
FINISHED |
| Object | exhaustion of ore deposits |
—
|
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: exhaustion of ore deposits | Statement: [Nevada ghost towns, mainCauseOfAbandonment, exhaustion of ore deposits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCauseOfAbandonment Context triple: [Nevada ghost towns, mainCauseOfAbandonment, exhaustion of ore deposits]
-
A.
abandonedReason
chosen
Indicates the reason or cause for which something was abandoned, discontinued, or given up.
-
B.
abandonmentType
Indicates the specific manner or category of how something or someone was abandoned in the described situation.
-
C.
reasonForDiscontinuation
Indicates that one entity specifies the cause or justification for stopping, ending, or withdrawing another entity, process, or activity.
-
D.
retreatCause
Indicates that one event, condition, or factor serves as the reason or trigger for a retreat by an entity.
-
E.
abandonment
Indicates the act of one party leaving, forsaking, or giving up responsibility for another party or thing.
- 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_69ee5bc2b2948190b458ad3f580af779 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 26, 2026, 8:10 p.m.