Triple
T7567370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwood, Ohio |
E178950
|
entity |
| Predicate | GMPlantClosed |
P77647
|
FINISHED |
| Object | 1987 |
—
|
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: 1987 | Statement: [Norwood, Ohio, GMPlantClosed, 1987]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GMPlantClosed Context triple: [Norwood, Ohio, GMPlantClosed, 1987]
-
A.
closedAsEnrichmentPlant
Indicates that a facility ceased operations specifically in its role as an enrichment plant.
-
B.
hasPlantSymbol
Indicates that an entity is associated with or represented by a particular plant as its symbolic emblem or sign.
-
C.
hasMajorPlant
Indicates that one entity possesses or hosts a primary or most significant plant facility or installation in relation to another entity.
-
D.
closedFor
Indicates that an entity is not available or accessible for use, entry, or operation during a specified time, condition, or reason.
-
E.
involvesPlant
Indicates that the relationship or action includes or pertains to a plant as a participating 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_69c69f2f80288190b95cceb4da92ab2b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f91c717881909c88901cc3b101c7 |
completed | March 27, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69c6f4dc485c819080da13e3b7f4f08f |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f59517648190ac0a9e9cba045dd5 |
completed | March 27, 2026, 9:24 p.m. |
Created at: March 27, 2026, 3:51 p.m.