Triple
T33071752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polyforum Cultural Siqueiros |
E846252
|
entity |
| Predicate | hasMuralTechnique |
P14965
|
FINISHED |
| Object | polyangular mural |
—
|
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: polyangular mural | Statement: [Polyforum Cultural Siqueiros, hasMuralTechnique, polyangular mural]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMuralTechnique Context triple: [Polyforum Cultural Siqueiros, hasMuralTechnique, polyangular mural]
-
A.
hasArtOrMurals
Indicates that one entity features or contains artworks or murals associated with another entity.
-
B.
artisticTechnique
chosen
Indicates the method, style, or process used to create or execute an artistic work.
-
C.
hasTechnique
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
D.
hasMuralsFrom
Indicates that a location or structure contains murals that originate from or were created in a specified place or time period.
-
E.
hasWallPaintingStyle
Indicates that an entity features or is associated with a particular style or type of wall painting.
- 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: May 1, 2026, 1:25 a.m.