Triple
T38604068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Żydaczów |
E934295
|
entity |
| Predicate | hasMulticulturalPast |
P89769
|
FINISHED |
| Object | Polish community |
—
|
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: Polish community | Statement: [Żydaczów, hasMulticulturalPast, Polish community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMulticulturalPast Context triple: [Żydaczów, hasMulticulturalPast, Polish community]
-
A.
hasMulticulturalTradition
chosen
Indicates that an entity possesses customs, practices, or heritage derived from or influenced by multiple cultural backgrounds.
-
B.
hasCulturalRoots
Indicates that something originates from, is shaped by, or is deeply connected to particular cultural traditions, practices, or heritage.
-
C.
hasDistinctCulturalHeritage
Indicates that an entity possesses a unique cultural background, traditions, or practices that distinguish it from other entities.
-
D.
hadLanguageDiversity
Indicates that an entity exhibited a range of different languages used or represented within it.
-
E.
historicalDiversity
Indicates that there has been variation or change in the composition, characteristics, or representation of something across different historical periods.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fef112398081909237c3872345968b |
completed | May 9, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69feefb14ec08190ab401987d8c84a23 |
completed | May 9, 2026, 8:26 a.m. |
Created at: May 3, 2026, 4:32 p.m.