Triple
T37675455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basilica of Sant’Eustachio in Rome |
E938079
|
entity |
| Predicate | hasFaçadeElement |
P31480
|
FINISHED |
| Object | central portal |
—
|
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: central portal | Statement: [Basilica of Sant’Eustachio in Rome, hasFaçadeElement, central portal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFaçadeElement Context triple: [Basilica of Sant’Eustachio in Rome, hasFaçadeElement, central portal]
-
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.
facadeFeature
chosen
Indicates that one element functions as a distinct architectural or design feature on the façade of another structure.
-
D.
facadePreserved
Indicates that the external front or face of a structure has been maintained or kept intact, typically while other parts may have been altered or redeveloped.
-
E.
façadeType
Indicates the specific kind or style of façade that characterizes or is applied to a building or structure.
- 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_69f76ed7b1408190ba8c93c53cb8becf |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
Created at: May 3, 2026, 4:18 p.m.