Triple
T25114642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iglesia de San Nicolás el Real |
E629092
|
entity |
| Predicate | hasArtisticWorks |
P1572
|
FINISHED |
| Object | church altarpieces |
—
|
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: church altarpieces | Statement: [Iglesia de San Nicolás el Real, hasArtisticWorks, church altarpieces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtisticWorks Context triple: [Iglesia de San Nicolás el Real, hasArtisticWorks, church altarpieces]
-
A.
hasArtworksFrom
Indicates that one entity possesses or includes artworks that originate from or are created by another entity.
-
B.
hasArtisticDiscipline
Indicates that one entity practices, specializes in, or is associated with a particular artistic discipline or field.
-
C.
hasArtisticActivity
Indicates that an entity engages in, participates in, or is associated with an artistic activity or creative practice.
-
D.
hasPublicArtwork
chosen
Indicates that a location or entity possesses or features artwork that is accessible to the general public.
-
E.
hasFamousArtwork
Indicates that an entity possesses or is associated with a well-known or widely recognized artwork.
- 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 18, 2026, 6:27 a.m.