Triple
T3158896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palacio de Justicia |
E66055
|
entity |
| Predicate | hasFacadeType |
P31480
|
FINISHED |
| Object | monumental neoclassical 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: monumental neoclassical façade | Statement: [Palacio de Justicia, hasFacadeType, monumental neoclassical façade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFacadeType Context triple: [Palacio de Justicia, hasFacadeType, monumental neoclassical façade]
-
A.
hasFacet
Indicates that an entity possesses a particular aspect, side, or dimension as one of its distinguishable parts or characteristics.
-
B.
facadeFeature
chosen
Indicates that one element functions as a distinct architectural or design feature on the façade of another structure.
-
C.
hasInterface
Indicates that one entity provides, exposes, or is connected through a defined interface to another entity.
-
D.
hasPlatformType
Indicates that an entity is associated with or characterized by a specific type or category of platform.
-
E.
hasFacilityType
Indicates that an entity possesses or is associated with a specific type or category of facility.
- 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada5ed82a08190a1bdcf18ee593c79 |
completed | March 8, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfbf0348190952a6bca8fc5fed1 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.