Triple
T24444624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manheim |
E616365
|
entity |
| Predicate | partlyRelocatedFor |
P62852
|
FINISHED |
| Object | lignite 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: lignite mining | Statement: [Manheim, partlyRelocatedFor, lignite mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partlyRelocatedFor Context triple: [Manheim, partlyRelocatedFor, lignite mining]
-
A.
partiallyRelocated
chosen
Indicates that an entity has been moved from its original location to a new one, but the relocation is incomplete or only affects part of the entity or its components.
-
B.
relocatedDuring
Indicates that an entity changed its location or place of residence within the time span of a specified event or period.
-
C.
relocatedAfter
Indicates that one entity moved or was transferred to a new location after another specified event or relocation occurred.
-
D.
relocated
Indicates that an entity has moved or been moved from one location or position to another.
-
E.
relocatedBetween
Indicates that an entity changed location from one place to another during a specified time interval or between two reference points.
- 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_69e2d7edca608190aafefc8877a1b4da |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29852c6908190ab5186cee3693625 |
completed | April 29, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:17 a.m.