Triple
T24340591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hambach open-pit mine |
E613500
|
entity |
| Predicate | causedResettlementOf |
P122121
|
FINISHED |
| Object | Manheim |
—
|
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: Manheim | Statement: [Hambach open-pit mine, causedResettlementOf, Manheim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causedResettlementOf Context triple: [Hambach open-pit mine, causedResettlementOf, Manheim]
-
A.
resettledBy
Indicates that an entity has been moved or established anew in a location or context by another agent or authority.
-
B.
influencedRelocationOf
chosen
Indicates that one entity played a causal or motivating role in another entity’s decision or action to move from one location to another.
-
C.
resettlementStart
Indicates the point in time when a process of relocating people or communities to a new place begins.
-
D.
displacedBy
Indicates that one entity has been moved, replaced, or forced out of its original position, role, or state by another entity.
-
E.
resettlementStatus
Indicates the current stage or condition of an entity’s relocation or re-establishment process in a new place.
- 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_69e2d7dcc5a08190b53691130d56cbc4 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2932461ec8190933bf1e56e0f647e |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:57 a.m.