Triple
T17122330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Machová |
E415498
|
entity |
| Predicate | typicalForCulture |
P66792
|
FINISHED |
| Object | Czech culture |
—
|
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: Czech culture | Statement: [Machová, typicalForCulture, Czech culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalForCulture Context triple: [Machová, typicalForCulture, Czech culture]
-
A.
popularCultureTrait
Indicates that an entity exhibits a characteristic, behavior, or element that is commonly recognized or influential within popular culture.
-
B.
basedInCulture
Indicates that an entity is situated within, originates from, or is fundamentally associated with a particular culture.
-
C.
cultureCharacteristic
chosen
Indicates that a particular trait, practice, or feature is a defining characteristic of a given culture.
-
D.
isCulturalStandardFor
Indicates that something is recognized or accepted as the customary or normative practice, value, or behavior within a particular culture or cultural context.
-
E.
culturalTradition
Indicates a relationship where certain practices, beliefs, or customs are recognized as part of a shared cultural heritage passed down within a group or society.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3e80ac2cc819084fab829917c950a |
completed | April 18, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69e35d6d20808190a38bb32e2294bc48 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:36 a.m.