Triple
T16626784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamilton Estate |
E403966
|
entity |
| Predicate | palaceSubsidenceCause |
P77074
|
FINISHED |
| Object | coal mining |
—
|
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 mining | Statement: [Hamilton Estate, palaceSubsidenceCause, coal mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: palaceSubsidenceCause Context triple: [Hamilton Estate, palaceSubsidenceCause, coal mining]
-
A.
subsidenceMechanism
chosen
Indicates the process or mechanism by which ground or surface subsidence occurs.
-
B.
causeOfDownfall
Indicates a factor, event, or agent that brings about the failure, ruin, or collapse of someone or something.
-
C.
roofCollapsed
Indicates that the roof of a structure has given way or fallen in, typically due to structural failure or external forces.
-
D.
ceasedSubductionBy
Indicates that a subduction process involving one tectonic plate or slab has stopped as a result of interaction with, or conditions imposed by, another plate or geological entity.
-
E.
naturalCaveCollapsed
Indicates that a naturally formed cave has undergone a structural failure resulting in its partial or complete collapse.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e375530ed081908337dc5c6360d733 |
completed | April 18, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.