Triple
T12532383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarnowskie Góry Lead-Silver-Zinc Mine |
E299600
|
entity |
| Predicate | significantPeriodOfActivity |
P10350
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Tarnowskie Góry Lead-Silver-Zinc Mine, significantPeriodOfActivity, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantPeriodOfActivity Context triple: [Tarnowskie Góry Lead-Silver-Zinc Mine, significantPeriodOfActivity, 16th century]
-
A.
hasSignificantActivity
Indicates that an entity exhibits a notable level or intensity of activity, performance, or operation relative to a defined threshold or context.
-
B.
evidenceOfActivity
Indicates that there is information or data supporting the occurrence or performance of a particular activity or action.
-
C.
peakActivity
Indicates that an entity is at its highest or most intense level of activity within a given period or context.
-
D.
activityTime
chosen
Indicates the time period during which an activity occurs or is scheduled to take place.
-
E.
partOfWorkPeriod
Indicates that a specific time span is contained within, and belongs to, a larger defined work period.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d9540d7b788190a0d57b098e90e491 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.