Triple
T38566526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Žarnovica |
E928234
|
entity |
| Predicate | hasMiningBackground |
P141935
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Žarnovica, hasMiningBackground, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMiningBackground Context triple: [Žarnovica, hasMiningBackground, yes]
-
A.
hasMiningActivity
Indicates that some form of mining operation or extraction activity is occurring at, involving, or associated with the referenced entity.
-
B.
hasIndustrialBackground
chosen
Indicates that an entity has prior experience, involvement, or roots in industrial work, sectors, or environments.
-
C.
hasMiningActivityType
Indicates that an entity is associated with a specific type or category of mining activity.
-
D.
isFormerMiningCommunity
Indicates that a place was historically a mining community but no longer functions primarily as one.
-
E.
hasBackground
Indicates that an entity possesses or is associated with a particular background, such as context, setting, or prior circumstances.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: May 3, 2026, 4:32 p.m.