Triple
T21940658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acre Time |
E541809
|
entity |
| Predicate | historicalChange |
P7789
|
FINISHED |
| Object | Brazil has modified Acre Time offset and coverage in past time zone reforms |
—
|
NE NERFINISHED |
How this triple was built (3 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: Brazil has modified Acre Time offset and coverage in past time zone reforms | Statement: [Acre Time, historicalChange, Brazil has modified Acre Time offset and coverage in past time zone reforms]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brazil has modified Acre Time offset and coverage in past time zone reforms Context triple: [Acre Time, historicalChange, Brazil has modified Acre Time offset and coverage in past time zone reforms]
-
A.
Brasília Time
Brasília Time is the standard time zone used in Brazil’s capital and much of the country’s eastern region, typically set at UTC−03:00.
-
B.
2011 Russian time zone reform
The 2011 Russian time zone reform was a nationwide adjustment of Russia’s timekeeping system that significantly altered the number and configuration of the country’s time zones and daylight saving practices.
-
C.
2014 Russian time zone reform
The 2014 Russian time zone reform was a nationwide adjustment of Russia’s timekeeping system that changed the number, boundaries, and UTC offsets of its time zones, including the abolition of permanent daylight saving time.
-
D.
Paraguay Summer Time
Paraguay Summer Time is the daylight saving time zone used in Paraguay, set one hour ahead of its standard time to align with neighboring regional schedules.
-
E.
America/Manaus
America/Manaus is the IANA time zone identifier representing the Amazon Time zone used in Manaus, Brazil.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Brazil has modified Acre Time offset and coverage in past time zone reforms Target entity description: Acre Time is a Brazilian time zone used in the western part of the country, particularly the state of Acre, whose offset and regional application have been adjusted through various national time zone reforms.
-
A.
Brasília Time
Brasília Time is the standard time zone used in Brazil’s capital and much of the country’s eastern region, typically set at UTC−03:00.
-
B.
2011 Russian time zone reform
The 2011 Russian time zone reform was a nationwide adjustment of Russia’s timekeeping system that significantly altered the number and configuration of the country’s time zones and daylight saving practices.
-
C.
2014 Russian time zone reform
The 2014 Russian time zone reform was a nationwide adjustment of Russia’s timekeeping system that changed the number, boundaries, and UTC offsets of its time zones, including the abolition of permanent daylight saving time.
-
D.
Paraguay Summer Time
Paraguay Summer Time is the daylight saving time zone used in Paraguay, set one hour ahead of its standard time to align with neighboring regional schedules.
-
E.
America/Manaus
America/Manaus is the IANA time zone identifier representing the Amazon Time zone used in Manaus, Brazil.
- F. None of above. chosen
Provenance (2 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_69e0c47e2e5c81909a7f74ce3de50911 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12420b1cc81909b375891aedc0979 |
completed | April 28, 2026, 9:18 p.m. |
Created at: April 16, 2026, 7:55 p.m.