Triple
T29887496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | São Sebastião do Rio de Janeiro |
E759055
|
entity |
| Predicate | municipalHolidayDate |
P31755
|
FINISHED |
| Object | January 20 |
—
|
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: January 20 | Statement: [São Sebastião do Rio de Janeiro, municipalHolidayDate, January 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalHolidayDate Context triple: [São Sebastião do Rio de Janeiro, municipalHolidayDate, January 20]
-
A.
hasMunicipalHoliday
chosen
Indicates that a particular place or jurisdiction observes a specific municipal holiday as part of its official local calendar.
-
B.
nationalHolidayDate
Indicates the specific calendar date on which a given national holiday is officially observed.
-
C.
holidayDateSystem
Indicates the system or convention used to determine and represent the date on which a holiday occurs.
-
D.
rankAmongHolidays
Indicates how a holiday is positioned or ordered in importance, popularity, or precedence relative to other holidays.
-
E.
hasOfficialHoliday
Indicates that a particular date, event, or period is formally recognized as an official holiday by an authority or governing body.
- 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_69f2245de2f48190a481404896b56254 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 29, 2026, 6 p.m.