Triple
T31909163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Círio de Nazaré |
E814634
|
entity |
| Predicate | coreEvent |
P49138
|
FINISHED |
| Object | main procession |
—
|
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: main procession | Statement: [Círio de Nazaré, coreEvent, main procession]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreEvent Context triple: [Círio de Nazaré, coreEvent, main procession]
-
A.
coreAction
Indicates the primary or central action that defines the main relationship or event occurring between the involved entities.
-
B.
mainEventFor
chosen
Indicates that one event is the primary or central event associated with another entity, such as a context, grouping, or larger occurrence.
-
C.
coMainEvent
Indicates that two or more events share equal primary status as the main featured events within the same program or occasion.
-
D.
eventCommanded
Indicates that one entity issued an order or directive for another entity to carry out a specific event or action.
-
E.
core
Indicates a central, most important, or foundational part of something in relation to its surrounding or supporting elements.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b1b92b9081909105e14626a3c04b |
completed | May 3, 2026, 2:23 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: May 1, 2026, 12:01 a.m.