Triple
T26956665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopewell Furnace National Historic Site |
E678923
|
entity |
| Predicate | closedAsIronWorks |
P105169
|
FINISHED |
| Object | 1883 |
—
|
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: 1883 | Statement: [Hopewell Furnace National Historic Site, closedAsIronWorks, 1883]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedAsIronWorks Context triple: [Hopewell Furnace National Historic Site, closedAsIronWorks, 1883]
-
A.
operatedAsIronworksUntil
chosen
Indicates that an entity functioned in the capacity of an ironworks up to a specified point in time.
-
B.
closedAsFoundry
Indicates that an entity has been shut down or decommissioned specifically in its role or status as a foundry.
-
C.
closedIn
Indicates that one entity is enclosed, contained, or surrounded within the boundaries or limits defined by 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.
closedAs
Indicates that one entity has been brought to an end, resolved, or made no longer active as a result of another entity or action.
- 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_69eeeb4e75f08190b14fc91ca4a91488 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 6:27 a.m.