Triple
T34361853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Iglesia Catedral de Santa María |
E881897
|
entity |
| Predicate | hasMainFacade |
P203530
|
FINISHED |
| Object | Baroque main 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 main façade | Statement: [Santa Iglesia Catedral de Santa María, hasMainFacade, Baroque main façade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainFacade Context triple: [Santa Iglesia Catedral de Santa María, hasMainFacade, Baroque main façade]
-
A.
hasFacadeBy
Indicates that one entity’s façade (front-facing exterior surface) is designed, created, or provided by another entity.
-
B.
hasFacadeSystem
Indicates that one entity possesses or is equipped with a particular façade system as part of its structure or design.
-
C.
hasMainForm
Indicates that one entity is the primary or canonical form of another related entity.
-
D.
hasMainPortal
Indicates that one entity serves as the primary or main portal (entry point or access interface) for another entity.
-
E.
hasMainStructure
Indicates that one entity serves as the primary or central structural component of another entity.
- 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_69f349be5c9c81908dc726ae1f4c68f2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a019d1407588190b3b9b83fca2e61fe |
completed | May 11, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_6a019c760e3081909cfe9c0603727e48 |
completed | May 11, 2026, 9:08 a.m. |
| PDg | Predicate description generation | batch_6a019d12c1208190940abb0736c389b0 |
completed | May 11, 2026, 9:10 a.m. |
Created at: May 1, 2026, 1:58 a.m.