Triple
T4660773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arlington Heights Historic District |
E102522
|
entity |
| Predicate | hasPeriodOfConstruction |
P22153
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Arlington Heights Historic District, hasPeriodOfConstruction, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeriodOfConstruction Context triple: [Arlington Heights Historic District, hasPeriodOfConstruction, 19th century]
-
A.
eraOfMajorConstruction
chosen
Indicates the time period during which the primary or most significant phase of construction for an entity took place.
-
B.
hasBuildingPeriod
Indicates that a building or structure is associated with a specific time period during which it was constructed or significantly developed.
-
C.
constructionDate
Indicates the date on which an entity (such as a building or structure) was constructed or completed.
-
D.
constructionTime
Indicates the duration or specific point in time required to construct or build an entity.
-
E.
buildingUsedSince
Indicates that a particular building has been in use starting from a specified point in time.
- 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_69bd43d823288190952279faa0d1d066 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd632a17cc8190bcdab0a13b89f5c0 |
completed | March 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69bd62126b0c81909ba3f21b21e30d54 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.