Triple
T16371631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Most |
E397576
|
entity |
| Predicate | reasonForRedevelopment |
P3337
|
FINISHED |
| Object | expansion of open-cast 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: expansion of open-cast coal mining | Statement: [Most, reasonForRedevelopment, expansion of open-cast coal mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForRedevelopment Context triple: [Most, reasonForRedevelopment, expansion of open-cast coal mining]
-
A.
reasonForRedesign
chosen
Indicates the underlying cause, motivation, or justification for performing a redesign.
-
B.
redevelopmentFor
Indicates a relationship where one entity is intended, designated, or used for the redevelopment of another entity.
-
C.
hasRedevelopmentGoal
Indicates that an entity is associated with a specific objective or target related to redevelopment or renewal activities.
-
D.
majorRedevelopmentFor
Indicates a significant redevelopment project or transformation that is being carried out for, or in relation to, a particular entity or site.
-
E.
hasConditionBeforeRedevelopment
Indicates that an entity possesses or exhibits a particular condition or state prior to its redevelopment.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2ff420d04819096ff12e08edf2f8b |
completed | April 18, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.