Triple
T24724510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vreoci |
E612405
|
entity |
| Predicate | hasMiningActivityNearby |
P144619
|
FINISHED |
| Object | lignite extraction |
—
|
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 extraction | Statement: [Vreoci, hasMiningActivityNearby, lignite extraction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMiningActivityNearby Context triple: [Vreoci, hasMiningActivityNearby, lignite extraction]
-
A.
hasMiningActivity
Indicates that some form of mining operation or extraction activity is occurring at, involving, or associated with the referenced entity.
-
B.
hasNearbyMine
Indicates that one entity is located close to or in the vicinity of a mine associated with another entity.
-
C.
hasCoalMineNearby
Indicates that a location or entity is situated close to at least one coal mine.
-
D.
hasMiningActivityType
chosen
Indicates that an entity is associated with a specific type or category of mining activity.
-
E.
hasMiningArea
Indicates that an entity possesses, controls, or is associated with a designated area where mining activities take 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_69e2d7d6e7a48190bb43b0d8bb1137a0 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 3:42 a.m.