Triple
T38548804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schemnitz |
E925047
|
entity |
| Predicate | notableForReferent |
—
|
GENERATED |
| Object | medieval mining townscape |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableForReferent Context triple: [Schemnitz, notableForReferent, medieval mining townscape]
-
A.
notableFor
chosen
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
B.
notablyRefersTo
Indicates that one entity makes a particularly significant or noteworthy reference to another entity, beyond a routine or incidental mention.
-
C.
notableDisplay
Indicates that something is prominently or distinctively presented in a way that draws special attention or recognition.
-
D.
notableTarget
Indicates that the subject is particularly significant, prominent, or noteworthy with respect to the specified target.
-
E.
notableElement
Indicates that an entity has a component, feature, or part that is especially significant, prominent, or noteworthy in relation to it.
- F. None of above.
Provenance (1 batch)
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_69f76eaeb69c8190b367df9330d6f6af |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.