Triple
T6008597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Lorenzo Church |
E133774
|
entity |
| Predicate | hasFaçadeType |
P31596
|
FINISHED |
| Object | Baroque stone façade |
—
|
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: Baroque stone façade | Statement: [San Lorenzo Church, hasFaçadeType, Baroque stone façade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFaçadeType Context triple: [San Lorenzo Church, hasFaçadeType, Baroque stone façade]
-
A.
façadeType
chosen
Indicates the specific kind or style of façade that characterizes or is applied to a building or structure.
-
B.
facadeFeature
Indicates that one element functions as a distinct architectural or design feature on the façade of another structure.
-
C.
façadeDescription
Indicates a textual description that characterizes the appearance, style, or features of a building’s façade.
-
D.
hasFacet
Indicates that an entity possesses a particular aspect, side, or dimension as one of its distinguishable parts or characteristics.
-
E.
façadeDesigner
Indicates that one entity is responsible for designing the façade (external face) of a building or structure for 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f154ca481909431baf4feecc16d |
completed | March 22, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c049e4daf4819099bf870dc700e0a2 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.