Triple
T26956658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopewell Furnace National Historic Site |
E678923
|
entity |
| Predicate | foundedAsIronPlantation |
P178014
|
FINISHED |
| Object | 1771 |
—
|
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: 1771 | Statement: [Hopewell Furnace National Historic Site, foundedAsIronPlantation, 1771]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsIronPlantation Context triple: [Hopewell Furnace National Historic Site, foundedAsIronPlantation, 1771]
-
A.
foundedInColony
Indicates that an entity was established or created during a period when the location in question was a colony under foreign rule.
-
B.
cityFoundedForPlant
Indicates that a city was established specifically to support, host, or serve a particular plant or industrial facility.
-
C.
foundedAsColonyFor
Indicates that one entity was established as a colony specifically for the benefit, use, or purposes of another entity.
-
D.
foundedAsTradingPostBy
Indicates that an entity was originally established as a trading post by a specified founder or founding group.
-
E.
foundedAs
Indicates the original name or form under which an organization, institution, or entity was first established.
- 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_69eeeb4e75f08190b14fc91ca4a91488 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f707f380388190954b79d52a321921 |
completed | May 3, 2026, 8:31 a.m. |
Created at: April 27, 2026, 6:27 a.m.