Triple
T1072878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarnów |
E23368
|
entity |
| Predicate | hasMinorityHeritage |
P1494
|
FINISHED |
| Object | Jewish heritage |
—
|
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: Jewish heritage | Statement: [Tarnów, hasMinorityHeritage, Jewish heritage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMinorityHeritage Context triple: [Tarnów, hasMinorityHeritage, Jewish heritage]
-
A.
hasMinorityIn
Indicates that one entity holds a non-controlling, minority ownership or stake in another entity.
-
B.
recognizedAsMinorityIn
Indicates that an entity is officially acknowledged or classified as belonging to a minority group within a specified context or jurisdiction.
-
C.
hasHeritage
chosen
Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
-
D.
hasSignificantPopulationGroup
Indicates that an entity contains or is associated with a notable or substantial subgroup of a population, distinguished by shared characteristics or attributes.
-
E.
notableMinorityIn
Indicates that an entity is a prominent or significant member of a minority group within a specified larger group, place, or context.
- 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_69a493ee1f908190992b5f0d1b04459b |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b92afad88190b7705923f71fc760 |
completed | March 1, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69a4b73844708190a16c9e9824ca2fb6 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.