Triple
T34433081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bakers Creek Falls |
E883878
|
entity |
| Predicate | hasNearestHistoricMiningTown |
P89210
|
FINISHED |
| Object | Hillgrove |
—
|
NE NERFINISHED |
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: Hillgrove | Statement: [Bakers Creek Falls, hasNearestHistoricMiningTown, Hillgrove]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearestHistoricMiningTown Context triple: [Bakers Creek Falls, hasNearestHistoricMiningTown, Hillgrove]
-
A.
containsMiningTown
Indicates that a location or area includes within its boundaries a town whose primary activity or identity is based on mining.
-
B.
locatedInHistoricMiningTown
Indicates that something is situated within a town historically associated with mining activity.
-
C.
hasNearbyFormerMiningCommunity
chosen
Indicates that an entity is located close to a community that previously hosted mining activities but is no longer an active mining site.
-
D.
isMiningTown
Indicates that a location is a town whose primary historical or economic basis is mining activities.
-
E.
wasRoyalMiningTownOf
Indicates that a town historically held official royal status and functioned as a designated center for mining activities under royal authority.
- 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ffc3f0b19c8190b5a749bc3cad21dd |
completed | May 9, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69ffc1b882808190932b2d43ea5537c9 |
completed | May 9, 2026, 11:22 p.m. |
Created at: May 1, 2026, 2 a.m.