Triple
T25032114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marianna, Pennsylvania |
E626874
|
entity |
| Predicate | hasLandUseHistoric |
P99800
|
FINISHED |
| Object | coal mine operations |
—
|
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: coal mine operations | Statement: [Marianna, Pennsylvania, hasLandUseHistoric, coal mine operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandUseHistoric Context triple: [Marianna, Pennsylvania, hasLandUseHistoric, coal mine operations]
-
A.
isHistoricDistrict
Indicates that an area has been officially recognized or designated as a historic district due to its historical, cultural, or architectural significance.
-
B.
hasHistoricDistrict
Indicates that an entity possesses or contains a designated historic district within its boundaries or domain.
-
C.
hasHeritageUse
chosen
Indicates that something is used, managed, or valued in a way that relates to cultural, historical, or natural heritage.
-
D.
housingTypeHistoric
Indicates that an entity’s housing type is classified based on historical or heritage-related characteristics.
-
E.
residenceHistoric
Indicates that a residence has historical significance or is formally recognized as a historic dwelling.
- 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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 18, 2026, 6:07 a.m.