Triple
T12501581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erwin, North Carolina |
E298835
|
entity |
| Predicate | millClosureYear |
P19867
|
FINISHED |
| Object | 2000 |
—
|
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: 2000 | Statement: [Erwin, North Carolina, millClosureYear, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: millClosureYear Context triple: [Erwin, North Carolina, millClosureYear, 2000]
-
A.
closureYear
chosen
Indicates the year in which an entity (such as an organization, facility, or service) ceased operations or was officially closed.
-
B.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
-
C.
exitYear
Indicates the year in which an entity leaves, finishes, or ceases its association with another entity or context.
-
D.
demolitionYearApprox
Indicates that an entity was demolished in or around a particular year, where the year is an approximate rather than an exact value.
-
E.
decommissioningEndDate
Indicates the date on which a decommissioning process or status for something is completed or officially ends.
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e8a706c8190873623eab7db607d |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d41f3cc8190a3331fb9a895306f |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:57 p.m.