Triple
T27528580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presidency of the Republic of Brazil |
E694905
|
entity |
| Predicate | workingResidence |
P1527
|
FINISHED |
| Object | Palácio do Planalto |
—
|
NE NERFINISHED |
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: Palácio do Planalto | Statement: [Presidency of the Republic of Brazil, workingResidence, Palácio do Planalto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workingResidence Context triple: [Presidency of the Republic of Brazil, workingResidence, Palácio do Planalto]
-
A.
residenceInWork
Indicates that an entity’s place of residence is located within or at the same site as their place of work.
-
B.
residesInWork
Indicates that a person or entity lives or is based within the location, setting, or environment defined by a particular work (such as a book, film, or other creative piece).
-
C.
otherResidence
Indicates that an entity has an additional or alternative place of residence beyond its primary home.
-
D.
ownedResidence
Indicates that one entity has ownership of a dwelling or place of residence associated with another entity.
-
E.
locationOfWork
chosen
Indicates the place or site where an entity performs its work or carries out its professional activities.
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f31e12c8190880b758fef6a07e0 |
completed | May 2, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69f623ac3a9c8190a6ee0c137b09e4b0 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:25 p.m.