Triple
T37777626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America/Sao_Paulo |
E941730
|
entity |
| Predicate | followsBrazilianCivilTime |
P200359
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [America/Sao_Paulo, followsBrazilianCivilTime, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsBrazilianCivilTime Context triple: [America/Sao_Paulo, followsBrazilianCivilTime, yes]
-
A.
relativeOffsetToBrasiliaTime
Indicates the time difference or offset between a given time reference and Brasília’s local time.
-
B.
paranaTime
Indicates that an event or state occurs at a time corresponding to the local time zone of Paraná (a specific regional time standard).
-
C.
hasTimezoneOnBoliviaSide
Indicates that an entity is associated with the time zone used on the Bolivian side of a border or boundary.
-
D.
followedByTimeZone
Indicates that one time zone chronologically succeeds another in a defined ordering or sequence.
-
E.
followsTimeZoneInDaylightSavingTime
Indicates that one entity adopts and observes the same time zone rules as another entity specifically during periods of daylight saving time.
- 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_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff84202eb081908ae21a54a4414d68 |
completed | May 9, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69ff833065e4819098579129d4ee17d3 |
completed | May 9, 2026, 6:55 p.m. |
| PDg | Predicate description generation | batch_69ff841f2f2081908d72d4f878c538a0 |
completed | May 9, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:19 p.m.