Triple
T21771199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mir mine |
E537431
|
entity |
| Predicate | transitionedToUndergroundMining |
P145894
|
FINISHED |
| Object | 2000s |
—
|
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: 2000s | Statement: [Mir mine, transitionedToUndergroundMining, 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transitionedToUndergroundMining Context triple: [Mir mine, transitionedToUndergroundMining, 2000s]
-
A.
hasUndergroundMine
Indicates that one entity possesses, controls, or contains an underground mine associated with it.
-
B.
undergroundMiningContinuedUntil
Indicates that the activity of underground mining persisted up to a specified time or event.
-
C.
integratedIntoUnderground
Indicates that something has been incorporated or absorbed into an underground system, structure, or environment.
-
D.
hasUndergroundOrgan
Indicates that an entity possesses an organ or structure that is located below the ground surface.
-
E.
hasUndergroundDepth
Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
- F. None of above. chosen
Provenance (4 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f031aea8c88190b4bc57df6f269ba6 |
completed | April 28, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 6:51 p.m.