Triple
T32344740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MMK 3 |
E826424
|
entity |
| Predicate | culturalField |
P81632
|
FINISHED |
| Object | visual arts |
—
|
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: visual arts | Statement: [MMK 3, culturalField, visual arts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culturalField Context triple: [MMK 3, culturalField, visual arts]
-
A.
culturalSphere
Indicates that one entity belongs to, is influenced by, or participates in the cultural domain, tradition, or milieu defined by another entity.
-
B.
culturalCategory
Indicates that one entity classifies or groups another entity according to a particular culture, tradition, or culturally defined type.
-
C.
culturalType
chosen
Indicates the classification of something according to its cultural category, style, or tradition.
-
D.
culturalLayer
Indicates the relationship in which something belongs to, originates from, or is associated with a particular cultural stratum, tradition, or level within a culture.
-
E.
culturalElements
Indicates a relationship where certain elements (such as practices, symbols, or artifacts) belong to, express, or characterize a particular culture or cultural 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 1, 2026, 12:48 a.m.