Triple
T24954038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anzac Day Eve match |
E624417
|
entity |
| Predicate | ceremonialFeatures |
P157272
|
FINISHED |
| Object | pre-game ceremony |
—
|
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: pre-game ceremony | Statement: [Anzac Day Eve match, ceremonialFeatures, pre-game ceremony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonialFeatures Context triple: [Anzac Day Eve match, ceremonialFeatures, pre-game ceremony]
-
A.
ceremonialUse
Indicates that something is used in a ritual, religious, or formal ceremony rather than for ordinary or practical purposes.
-
B.
ceremonialDressFeature
Indicates that one entity is a characteristic, component, or distinguishing element of another entity’s ceremonial dress or attire.
-
C.
ceremonialFocus
Indicates that one entity serves as the central object, site, or theme around which a ceremony or ritual is organized or directed.
-
D.
ceremonialAction
Indicates an action performed as part of a formal ceremony or ritual, typically following prescribed traditions or symbolic procedures.
-
E.
ceremonialSymbol
Indicates that one entity serves as a symbol used in a formal or ritual ceremony for another entity or concept.
- 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_69e2ff23a3a88190b1b9743fe5e15f94 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4240239e88190aa04201eb7d8a80b |
completed | May 1, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f423637bec8190a1701421ac86a3b7 |
completed | May 1, 2026, 3:52 a.m. |
Created at: April 18, 2026, 5:57 a.m.