Triple
T17088396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Dodge, Iowa |
E414659
|
entity |
| Predicate | hasHistoricIndustrySite |
P3008
|
FINISHED |
| Object | gypsum quarries |
—
|
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: gypsum quarries | Statement: [Fort Dodge, Iowa, hasHistoricIndustrySite, gypsum quarries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricIndustrySite Context triple: [Fort Dodge, Iowa, hasHistoricIndustrySite, gypsum quarries]
-
A.
hasIndustrialHeritage
Indicates that an entity possesses or is associated with historically significant industrial sites, structures, or practices.
-
B.
hasHistoricSite
Indicates that an entity possesses, contains, or is associated with a place recognized for its historical significance.
-
C.
hasHistoricIndustry
chosen
Indicates that an entity has been associated with a notable or historically significant industry or industrial activity in the past.
-
D.
hasIndustrialSiteIn
Indicates that an entity possesses, operates, or is responsible for an industrial facility located within a specified place or area.
-
E.
hasAdjacentHistoricSite
Indicates that one place is directly next to or very near another place that is recognized as a historic site.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe92e488190b947287a968086d5 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.