Triple
T34085506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shravana Putrada Ekadashi |
E874165
|
entity |
| Predicate | paranaTime |
P178210
|
FINISHED |
| Object | breaking the fast on Dwadashi |
—
|
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: breaking the fast on Dwadashi | Statement: [Shravana Putrada Ekadashi, paranaTime, breaking the fast on Dwadashi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paranaTime Context triple: [Shravana Putrada Ekadashi, paranaTime, breaking the fast on Dwadashi]
-
A.
distanceToParanáApproxKm
Indicates an approximate distance, measured in kilometers, between a subject entity and the Paraná location or region.
-
B.
relativeOffsetToBrasiliaTime
Indicates the time difference or offset between a given time reference and Brasília’s local time.
-
C.
BrazilNeededResult
Indicates that Brazil required or depended on a particular outcome or result to occur or be achieved.
-
D.
arrivalDateInBrazil
Indicates the date on which an entity arrives or is scheduled to arrive in Brazil.
-
E.
distanceToPantanal
Indicates the spatial distance between a given location and the Pantanal region.
- 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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70c53062c8190b4cb7be22ab00bc7 |
completed | May 3, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70b94784c8190970d654e066eb50d |
completed | May 3, 2026, 8:47 a.m. |
Created at: May 1, 2026, 1:52 a.m.