Triple
T19884645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Câmara dos Deputados |
E477864
|
entity |
| Predicate | sessionRoomLocation |
P137703
|
FINISHED |
| Object | east semi-sphere of the National Congress building |
—
|
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: east semi-sphere of the National Congress building | Statement: [Câmara dos Deputados, sessionRoomLocation, east semi-sphere of the National Congress building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sessionRoomLocation Context triple: [Câmara dos Deputados, sessionRoomLocation, east semi-sphere of the National Congress building]
-
A.
seatLocatedIn
Indicates that a seat is situated within or belongs to a specific location or area.
-
B.
seatLocatedAt
Indicates that a seat is positioned or situated at a specific location or place.
-
C.
slotLocation
Indicates the specific position or compartment within a larger container or system where an item is placed or assigned.
-
D.
seatLocation
Indicates the spatial position or placement of a seat relative to a reference point or environment.
-
E.
hallLocatedNear
Indicates that a hall is situated close to another specified place or entity in physical space.
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659093df081909d3be9c3caeb79ba |
completed | April 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:52 p.m.