Triple
T2805263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auburn Gresham |
E54036
|
entity |
| Predicate | housingStockEra |
P32323
|
FINISHED |
| Object | primarily early to mid-20th 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: primarily early to mid-20th century | Statement: [Auburn Gresham, housingStockEra, primarily early to mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: housingStockEra Context triple: [Auburn Gresham, housingStockEra, primarily early to mid-20th century]
-
A.
hasHousingStockAge
chosen
Indicates the relationship between an entity and the age or period of construction of its available housing stock.
-
B.
residenceHistoric
Indicates that a residence has historical significance or is formally recognized as a historic dwelling.
-
C.
houseFounded
Indicates that an entity (such as a house, organization, or lineage) was established or created by another entity or at a specific time.
-
D.
urbanDevelopmentEra
Indicates the historical period or phase during which significant urban development or transformation of a place occurred.
-
E.
hasNearbyHistoricalEstate
Indicates that one entity is located close to another entity that is a recognized historical estate.
- 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_69ab49dcee188190b5c6eca9ae9e3469 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde2ec2ac8190bd702ad3eafb6aed |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd059f308190853191f6ffe2bc6f |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.