Triple
T30483134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onze-Lieve-Vrouwekerk Brugge |
E775641
|
entity |
| Predicate | artistOfNotableArtwork |
P132719
|
FINISHED |
| Object | Michelangelo |
—
|
NE NERFINISHED |
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: Michelangelo | Statement: [Onze-Lieve-Vrouwekerk Brugge, artistOfNotableArtwork, Michelangelo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artistOfNotableArtwork Context triple: [Onze-Lieve-Vrouwekerk Brugge, artistOfNotableArtwork, Michelangelo]
-
A.
notableArtist
Indicates that the subject is an artist who is widely recognized or distinguished for their work.
-
B.
artistOfPublicArt
Indicates that one entity is the artist or creator responsible for a particular piece of public art.
-
C.
composerOfDepictingWork
Indicates that an entity is the composer of a musical work that is itself a depiction or representation of another entity or subject.
-
D.
hasArtistOfNotableWork
chosen
Indicates that an entity is associated with the artist who created a notable work related to that entity.
-
E.
notableArtObject
Indicates a relationship where an entity is recognized as an art object of particular significance, prominence, or cultural importance in connection to another entity.
- 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 8:13 p.m.