Triple
T33861234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Lady of Brazil |
E867927
|
entity |
| Predicate | notAnOfficialOfficeIn |
P75395
|
FINISHED |
| Object | Brazilian legal system |
—
|
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: Brazilian legal system | Statement: [First Lady of Brazil, notAnOfficialOfficeIn, Brazilian legal system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notAnOfficialOfficeIn Context triple: [First Lady of Brazil, notAnOfficialOfficeIn, Brazilian legal system]
-
A.
notOfficialIn
chosen
Indicates that an entity does not hold an official role, status, or position within a specified organization, group, or jurisdiction.
-
B.
notOfficialNameOf
Indicates that a given name or label is used for an entity but is not its official or formally recognized name.
-
C.
isOfficialOfficeOf
Indicates that one entity serves as the formally recognized office or headquarters associated with another entity.
-
D.
notOfficialSymbolOf
Indicates that something is explicitly not recognized or designated as the official symbol of a given entity.
-
E.
notOfficialCodeOf
Indicates that one entity is not the formally recognized or authorized code designation for the other entity.
- 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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5a4f7881909324eb3c20ca96f1 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.