Triple
T21547249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duquesne |
E531656
|
entity |
| Predicate | historicalSiteType |
P46970
|
FINISHED |
| Object | steel mill town |
—
|
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: steel mill town | Statement: [Duquesne, historicalSiteType, steel mill town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalSiteType Context triple: [Duquesne, historicalSiteType, steel mill town]
-
A.
historicLocationType
chosen
Indicates the specific kind or category of a place based on its historical significance or role.
-
B.
heritageSiteTypeNearby
Indicates that a particular type of heritage site is located in close proximity to the referenced entity.
-
C.
significantPlaceType
Indicates the type or category of place that holds particular significance in relation to the subject.
-
D.
heritageType
Indicates the classification of an entity’s cultural or natural heritage category or type within a heritage framework.
-
E.
culturalSite
Indicates that one entity is recognized or designated as a cultural site associated with or located in relation to another entity.
- 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_69e0c45f17148190949c330ab9c27706 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeb58fb6608190a58cd00ecf560834 |
completed | April 27, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:28 p.m.