Triple
T27360454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basilica of Saint-Barthélemy, Liège |
E685805
|
entity |
| Predicate | baptismalFontMaterial |
P163100
|
FINISHED |
| Object | bronze |
—
|
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: bronze | Statement: [Basilica of Saint-Barthélemy, Liège, baptismalFontMaterial, bronze]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baptismalFontMaterial Context triple: [Basilica of Saint-Barthélemy, Liège, baptismalFontMaterial, bronze]
-
A.
baptismalFontUsedFor
Indicates that a particular baptismal font is used to perform or conduct a specific baptism or set of baptisms.
-
B.
hasBaptismalFont
Indicates that a place or structure contains or is equipped with a baptismal font used for performing baptisms.
-
C.
baptismalFontArtist
Indicates that an entity is the artist or creator responsible for designing or making a particular baptismal font.
-
D.
baptismAssociatedWith
Indicates a relationship in which an entity is connected or related to a baptism event, such as by participation, performance, location, or contextual association.
-
E.
baptismPlace
Indicates the place where an individual was baptized.
- F. None of above. chosen
Provenance (4 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f63639a84c81909d700a539b458b42 |
completed | May 2, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 27, 2026, 11:53 a.m.