Triple
T62097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Independence Day (Mexico) |
E1233
|
entity |
| Predicate | mainCeremony |
P3305
|
FINISHED |
| Object | presidential reenactment of the Grito de Dolores |
—
|
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: presidential reenactment of the Grito de Dolores | Statement: [Independence Day (Mexico), mainCeremony, presidential reenactment of the Grito de Dolores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCeremony Context triple: [Independence Day (Mexico), mainCeremony, presidential reenactment of the Grito de Dolores]
-
A.
ceremonyType
chosen
Indicates the specific kind or category of ceremony associated with an event or relationship.
-
B.
ceremonyLocation
Indicates the place where a ceremony is held or takes place.
-
C.
ceremonyHeldOn
Indicates that a specific ceremony took place on a particular date or day.
-
D.
ceremonialRole
Indicates that an entity holds a formal, often symbolic or honorific, position or function within a ceremony or ritual context.
-
E.
languageOfCeremony
Indicates the language in which a ceremony is conducted or officially performed.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a251f74b0881909ad89127b8171277 |
completed | Feb. 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69a24ea242c8819086fe00bf01e6523e |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.