Triple
T25178457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Grand Old Flag |
E630515
|
entity |
| Predicate | celebratoryFunction |
P134250
|
FINISHED |
| Object | victory celebration |
—
|
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: victory celebration | Statement: [The Grand Old Flag, celebratoryFunction, victory celebration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: celebratoryFunction Context triple: [The Grand Old Flag, celebratoryFunction, victory celebration]
-
A.
isCelebratoryOf
Indicates that something expresses celebration, honor, or festive recognition directed toward a particular event, person, or occasion.
-
B.
publicCelebration
Indicates a relationship where an event, achievement, or occasion is celebrated openly and collectively in a public setting.
-
C.
celebrationAssociatedWith
chosen
Indicates a relationship where a celebration is connected to, linked with, or held in relation to a particular entity, event, or context.
-
D.
celebrationFocus
Indicates that the primary subject or emphasis of a celebration is directed toward a particular entity or theme.
-
E.
celebrationReason
Indicates the reason or cause for which a celebration is being held.
- 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46dc2ac088190a629119847b6097e |
completed | May 1, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 12:35 p.m.