Triple
T5460931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brazilian government |
E122590
|
entity |
| Predicate | legislativeTermLengthDeputies |
P10497
|
FINISHED |
| Object | 4 years |
—
|
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: 4 years | Statement: [Brazilian government, legislativeTermLengthDeputies, 4 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legislativeTermLengthDeputies Context triple: [Brazilian government, legislativeTermLengthDeputies, 4 years]
-
A.
orderOfDeputies
Indicates the hierarchical sequence or ranking of deputies within a governing or organizational structure.
-
B.
parliamentaryTerm
chosen
Indicates the specific legislative session or fixed period of time during which a parliament is formally in office and exercises its authority.
-
C.
electedMembers
Indicates that certain individuals have been chosen through an election process to serve as members of a specific body or organization.
-
D.
legislativePeriod
Indicates the specific legislative term or session during which an action, event, or status is valid or took place.
-
E.
deputyOf
Indicates that one entity serves as the subordinate or second-in-command to another, acting with delegated authority on their behalf.
- 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_69bd4643f16081908d7f29e08096115a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a0d96c8190bd1299edbf764bbb |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.