Triple
T4883400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rossio railway station |
E109382
|
entity |
| Predicate | hasFaçade |
P31596
|
FINISHED |
| Object | Neo-Manueline 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: Neo-Manueline façade | Statement: [Rossio railway station, hasFaçade, Neo-Manueline façade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFaçade Context triple: [Rossio railway station, hasFaçade, Neo-Manueline façade]
-
A.
facadeFeature
Indicates that one element functions as a distinct architectural or design feature on the façade of another structure.
-
B.
façadeDescription
Indicates a textual description that characterizes the appearance, style, or features of a building’s façade.
-
C.
façadeType
chosen
Indicates the specific kind or style of façade that characterizes or is applied to a building or structure.
-
D.
façadeDesigner
Indicates that one entity is responsible for designing the façade (external face) of a building or structure for another entity.
-
E.
hasFoyer
Indicates that an entity includes or is equipped with a foyer as part of its structure or layout.
- 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_69bd440f71348190b99938e59fb7f9a1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddfff0c81908fb148a6f6508334 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2be5e881909f6ec9c3bcde49f3 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:27 p.m.