Triple
T16388768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basilica of Saint Laurence Outside the Walls |
E397992
|
entity |
| Predicate | hasApseMosaic |
P44624
|
FINISHED |
| Object | mosaic of Christ with saints |
—
|
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: mosaic of Christ with saints | Statement: [Basilica of Saint Laurence Outside the Walls, hasApseMosaic, mosaic of Christ with saints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApseMosaic Context triple: [Basilica of Saint Laurence Outside the Walls, hasApseMosaic, mosaic of Christ with saints]
-
A.
hasMosaic
chosen
Indicates that one entity possesses, contains, or is decorated with a mosaic.
-
B.
hasApse
Indicates that a structure or building possesses an apse, typically a semicircular or polygonal recess, as one of its architectural features.
-
C.
hasMosaicsBy
Indicates that something contains or features mosaics that were created by a specified agent or creator.
-
D.
hasMesa
Indicates that an entity possesses, contains, or is associated with a mesa (a flat-topped elevated landform).
-
E.
hasMosaicSubject
Indicates that something is the depicted subject or main theme represented within a mosaic.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e3263f18988190800b921381d60c1b |
completed | April 18, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.