Triple
T20587396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empire, Nevada |
E505820
|
entity |
| Predicate | companyTownClosed |
P140670
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Empire, Nevada, companyTownClosed, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companyTownClosed Context triple: [Empire, Nevada, companyTownClosed, 2011]
-
A.
isCompanyTownOf
Indicates that a town is economically and socially dominated or controlled by a particular company, typically through ownership of major housing, services, and employment.
-
B.
isCompanyTownFor
Indicates that one location functions as a company town whose economy, services, or governance are predominantly controlled or dominated by a specific company.
-
C.
closedCityDuring
Indicates that a city is not accessible or operational during a specified time period or interval.
-
D.
hasClosedCity
Indicates that a country or region contains a city that is restricted or closed to general public access.
-
E.
wasClosedCity
Indicates that a city was officially designated as a "closed city," restricting access, residency, or movement due to security, military, or political reasons.
- 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_69e0b4b9669c8190b8e81fc72817d42c |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a977fb18819085fee5cf5d45c1b0 |
completed | April 20, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:40 a.m.