Triple
T1170390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Federal Court building in Brasília |
E24896
|
entity |
| Predicate | hasPublicPlazaFront |
P13926
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Supreme Federal Court building in Brasília, hasPublicPlazaFront, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicPlazaFront Context triple: [Supreme Federal Court building in Brasília, hasPublicPlazaFront, yes]
-
A.
hasPedestrianPlazaOn
Indicates that a pedestrian plaza is located on, or directly associated with, a specified surface, structure, or area.
-
B.
hasPlaza
chosen
Indicates that an entity includes, contains, or is associated with a plaza as part of its structure or grounds.
-
C.
hasPromenade
Indicates that one entity features or includes a promenade, typically as a designated walkway or leisure area associated with it.
-
D.
hasCourtyard
Indicates that one entity includes, features, or is characterized by the presence of a courtyard.
-
E.
isPublicBuilding
Indicates that a building is designated for public use, access, or service rather than being privately owned or restricted.
- 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_69a494082a7c819095004f423f294a64 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bce972cc8190bce0b77cfda6da41 |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5656948190b0b1d5446ad06005 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.