Triple
T1104971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saugus Iron Works National Historic Site |
E25467
|
entity |
| Predicate | originalConstructionEnd |
P1511
|
FINISHED |
| Object | 1650s |
—
|
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: 1650s | Statement: [Saugus Iron Works National Historic Site, originalConstructionEnd, 1650s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalConstructionEnd Context triple: [Saugus Iron Works National Historic Site, originalConstructionEnd, 1650s]
-
A.
originalBuildingConstructed
Indicates that a particular building was initially constructed in its original form or configuration.
-
B.
constructionCompleted
chosen
Indicates that a construction process or project has been fully finished and reached its completed state.
-
C.
constructionTime
Indicates the duration or specific point in time required to construct or build an entity.
-
D.
constructionStartedBy
Indicates that the construction of something was initiated or begun by a particular agent or entity.
-
E.
eraOfMajorConstruction
Indicates the time period during which the primary or most significant phase of construction for an entity took place.
- 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9e21f048190bf4b63dd2c7c7641 |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b74877748190b78cd8847ee4fa7a |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:43 p.m.