Triple
T9177825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Corn Ceremony |
E220244
|
entity |
| Predicate | prohibitsBeforeCeremony |
P86674
|
FINISHED |
| Object | eating new corn |
—
|
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: eating new corn | Statement: [Green Corn Ceremony, prohibitsBeforeCeremony, eating new corn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prohibitsBeforeCeremony Context triple: [Green Corn Ceremony, prohibitsBeforeCeremony, eating new corn]
-
A.
hasPublicCeremony
Indicates that a public ceremony is held or conducted in relation to the subject entity.
-
B.
isCeremonial
Indicates that something is associated with, intended for, or used in a formal ceremony or ritual rather than for ordinary or practical purposes.
-
C.
isCeremoniallyDistinctFrom
Indicates that two entities are formally separated or differentiated from each other within a ritual, ceremonial, or symbolic context.
-
D.
ceremonyTiming
Indicates the temporal relationship specifying when a ceremony occurs or is scheduled to occur.
-
E.
premiereOccasion
Indicates the event or context in which something (such as a work, show, or product) is first publicly presented or launched.
- 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc24eeb988190af82dfba49aac2f8 |
completed | April 1, 2026, 6:59 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc66d7bf648190b8bff5b584b84975 |
completed | April 1, 2026, 12:29 a.m. |
Created at: March 30, 2026, 7:23 p.m.