Triple
T28660773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarraconensis |
E725460
|
entity |
| Predicate | hadMajorMiningArea |
P99464
|
FINISHED |
| Object | Las Médulas |
—
|
NE NERFINISHED |
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: Las Médulas | Statement: [Tarraconensis, hadMajorMiningArea, Las Médulas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadMajorMiningArea Context triple: [Tarraconensis, hadMajorMiningArea, Las Médulas]
-
A.
eraOfMajorMiningActivity
Indicates the time period during which significant or primary mining operations took place for the associated entity.
-
B.
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.
-
C.
hasCoalMiningHistory
Indicates that an entity has a past or ongoing involvement in coal mining activities or industry.
-
D.
locatedInMiningDistrict
chosen
Indicates that one entity is situated within the geographic or administrative boundaries of a specified mining district.
-
E.
wasMajorMiningTownInCentury
Indicates that a town was a significant center of mining activity during a specified century.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:57 a.m.