Triple
T28323171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neuseenland lake district |
E717331
|
entity |
| Predicate | dominantResourcePreviouslyMined |
P153353
|
FINISHED |
| Object | lignite |
—
|
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 | Statement: [Neuseenland lake district, dominantResourcePreviouslyMined, lignite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantResourcePreviouslyMined Context triple: [Neuseenland lake district, dominantResourcePreviouslyMined, lignite]
-
A.
wasExtensivelyMinedIn
Indicates that a location or resource was subject to intensive or large-scale mining activity during a specified time or by a specified agent.
-
B.
isMinedIn
chosen
Indicates that a resource or material is extracted or obtained from a particular location or site.
-
C.
historicallySuppliedOreTo
Indicates that one entity provided ore to another entity as a supplier during a past historical period.
-
D.
minerRepresents
Indicates that a miner acts on behalf of, or serves as a representative or proxy for, another entity in a given context.
-
E.
minedOn
Indicates that a resource or material was extracted from a particular location or source on a specific date or time.
- 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 28, 2026, 12:26 a.m.