Triple
T33663999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashton Historic District |
E862432
|
entity |
| Predicate | landUseHistoric |
P131586
|
FINISHED |
| Object | industrial |
—
|
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: industrial | Statement: [Ashton Historic District, landUseHistoric, industrial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landUseHistoric Context triple: [Ashton Historic District, landUseHistoric, industrial]
-
A.
historicalUseOfArea
chosen
Indicates how an area was used or what activities occurred there during a past period.
-
B.
historicalHabitat
Indicates that an entity previously lived, occurred, or was distributed within a particular habitat or environment in the past.
-
C.
housingTypeHistoric
Indicates that an entity’s housing type is classified based on historical or heritage-related characteristics.
-
D.
formerLandUse
Indicates the type of land use that characterized a location prior to its current or present use.
-
E.
historicUsePersistsIn
Indicates that a practice, feature, or condition originating in the past continues to exist or be applied in the present.
- 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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fa36f640819098051eff7e5a5787 |
completed | May 3, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:42 a.m.