Triple
T37242393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seitendorf, Silesia |
E923746
|
entity |
| Predicate | hasMixedCulturalHeritage |
P177547
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Seitendorf, Silesia, hasMixedCulturalHeritage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMixedCulturalHeritage Context triple: [Seitendorf, Silesia, hasMixedCulturalHeritage, true]
-
A.
hasEthnicallyMixedPopulation
Indicates that a population is composed of people from multiple distinct ethnic groups rather than being ethnically homogeneous.
-
B.
mixedAncestry
Indicates that an entity has ancestry derived from more than one distinct lineage, group, or origin.
-
C.
culturalMixtureOf
chosen
Indicates that something embodies or results from the combination or blending of two or more distinct cultures.
-
D.
hasDistinctCulturalHeritage
Indicates that an entity possesses a unique cultural background, traditions, or practices that distinguish it from other entities.
-
E.
hasCulturalRoots
Indicates that something originates from, is shaped by, or is deeply connected to particular cultural traditions, practices, or heritage.
- 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_69f76ea9fee88190a589f661d95a7189 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: May 3, 2026, 4:15 p.m.