Triple
T16232932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upham Park Historic District |
E394032
|
entity |
| Predicate | typicalConstructionEra |
P22153
|
FINISHED |
| Object | early 1900s |
—
|
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: early 1900s | Statement: [Upham Park Historic District, typicalConstructionEra, early 1900s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalConstructionEra Context triple: [Upham Park Historic District, typicalConstructionEra, early 1900s]
-
A.
eraOfMajorConstruction
chosen
Indicates the time period during which the primary or most significant phase of construction for an entity took place.
-
B.
constructionCentury
Indicates the century during which something was constructed or built.
-
C.
estimatedConstructionEndCentury
Indicates the century in which the construction of something is estimated to have been completed.
-
D.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
-
E.
historical era
Indicates the broad historical period or epoch during which an entity, event, or phenomenon took place or is associated.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e23d2b0cc48190853919135d5a172a |
completed | April 17, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.