Triple
T15662514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shad Thames |
E376600
|
entity |
| Predicate | declinedAsIndustrialArea |
P119654
|
FINISHED |
| Object | 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: 20th century | Statement: [Shad Thames, declinedAsIndustrialArea, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declinedAsIndustrialArea Context triple: [Shad Thames, declinedAsIndustrialArea, 20th century]
-
A.
isIndustrialAreaOf
Indicates that a location functions primarily as an industrial zone or district associated with a specified area or jurisdiction.
-
B.
hasIndustrialAreaType
Indicates that an entity’s industrial area is classified as a specific type or category of industrial zone.
-
C.
hasIndustrialZoning
Indicates that a given area or property is designated for industrial use under zoning regulations.
-
D.
locatedInFormerIndustrialArea
Indicates that an entity is situated within an area that was previously used for industrial purposes but is no longer active as such.
-
E.
connectsToIndustrialArea
Indicates that one entity has a direct link, route, or access connection to an industrial area.
- F. None of above. chosen
Provenance (4 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f0e2668819092e52712cddd0721 |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:15 a.m.