Triple
T35895620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jáchymov silver mines |
E1038213
|
entity |
| Predicate | helpedMake |
P33868
|
FINISHED |
| Object | Jáchymov a major European mining center |
—
|
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: Jáchymov a major European mining center | Statement: [Jáchymov silver mines, helpedMake, Jáchymov a major European mining center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpedMake Context triple: [Jáchymov silver mines, helpedMake, Jáchymov a major European mining center]
-
A.
helpsProduce
Indicates that one entity contributes to or facilitates the creation, generation, or production of another entity.
-
B.
helpedCause
chosen
Indicates that one entity contributed to bringing about, enabling, or facilitating an outcome or event involving another entity.
-
C.
madeTo
Indicates that one entity is created, produced, or constructed for the purpose, use, or benefit of another entity.
-
D.
usesMake
Indicates that one entity employs, applies, or utilizes another entity as a means, tool, or method to achieve some purpose.
-
E.
saidToHaveMade
Indicates that one entity is reported or alleged to have created, produced, or caused another entity or outcome.
- 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_69f76e2190f88190beb2eed798a4ef01 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:06 p.m.