Triple
T9982290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breage |
E196482
|
entity |
| Predicate | hasIndustryHeritage |
P2411
|
FINISHED |
| Object | tin 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: tin mining | Statement: [Breage, hasIndustryHeritage, tin mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndustryHeritage Context triple: [Breage, hasIndustryHeritage, tin mining]
-
A.
hasIndustrialHeritage
chosen
Indicates that an entity possesses or is associated with historically significant industrial sites, structures, or practices.
-
B.
hasHeritage
Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
-
C.
hasHistoricIndustry
Indicates that an entity has been associated with a notable or historically significant industry or industrial activity in the past.
-
D.
isPartOfHeritage
Indicates that something belongs to, contributes to, or is recognized as a component of a broader cultural, historical, or natural heritage.
-
E.
hasHeritageFocus
Indicates that something is primarily concerned with, dedicated to, or centered around heritage-related themes, values, or preservation.
- 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_69ca82efbce081908179b4b9c65096eb |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb8bca41081909c04fb77603403b9 |
completed | April 2, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:49 p.m.