Triple
T23400277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sapê |
E559483
|
entity |
| Predicate | timezoneAbbreviation |
P12624
|
FINISHED |
| Object | BRT |
—
|
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: BRT | Statement: [Sapê, timezoneAbbreviation, BRT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timezoneAbbreviation Context triple: [Sapê, timezoneAbbreviation, BRT]
-
A.
zoneAbbreviation
Indicates that one entity is the abbreviated or short-form representation of a particular zone associated with another entity.
-
B.
DSTAbbreviation
Indicates that one entity is the standard abbreviated form used to represent another entity related to daylight saving time.
-
C.
includesTimeZoneAbbreviation
Indicates that something explicitly contains or specifies a time zone abbreviation as part of its representation or data.
-
D.
timeZoneName
Indicates the specific time zone designation (such as its standard name or label) associated with an entity.
-
E.
timeZoneDesignation
chosen
Indicates the specific time zone label or code assigned to an entity for representing its local time.
- 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_69e24549610c8190a069d6411ce5f661 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a4dedfcc8190ab93cec3c3d15c53 |
completed | April 29, 2026, 6:27 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:37 p.m.