Triple
T1170396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Federal Court building in Brasília |
E24896
|
entity |
| Predicate | hasPilotis |
P24579
|
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, hasPilotis, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPilotis Context triple: [Supreme Federal Court building in Brasília, hasPilotis, yes]
-
A.
hasPier
Indicates that a location or structure possesses or includes a pier as part of its features.
-
B.
hasPavilion
Indicates that one entity possesses, includes, or is associated with a pavilion as part of its structure, property, or facilities.
-
C.
hasBalustrades
Indicates that one entity features or is equipped with balustrades as part of its structure or design.
-
D.
hasParapet
Indicates that an object, structure, or area is equipped with or bounded by a parapet (a low protective wall or barrier along an edge).
-
E.
hasNave
Indicates that one entity (typically a building or structure) possesses or includes a nave as a distinct architectural part.
- 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_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. |
| PDg | Predicate description generation | batch_69a4bbd7ff1881908c943ecdfea59e81 |
completed | March 1, 2026, 10:21 p.m. |
Created at: March 1, 2026, 7:45 p.m.