Triple
T19141566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hen Egg |
E468569
|
entity |
| Predicate | commissionedForOccasion |
P56481
|
FINISHED |
| Object | Easter 1885 |
—
|
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: Easter 1885 | Statement: [Hen Egg, commissionedForOccasion, Easter 1885]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commissionedForOccasion Context triple: [Hen Egg, commissionedForOccasion, Easter 1885]
-
A.
specialOccasion
Indicates that an event or situation is associated with a notable or exceptional occasion, such as a celebration, milestone, or culturally significant date.
-
B.
creationOccasion
Indicates the specific event, context, or circumstances during which something was created.
-
C.
createdOnOccasionOf
chosen
Indicates that something was created specifically for, or in direct connection with, a particular event, occasion, or circumstance.
-
D.
premiereOccasion
Indicates the event or context in which something (such as a work, show, or product) is first publicly presented or launched.
-
E.
commissionedFor
Indicates that something was formally requested or created to serve a specific purpose, project, or recipient.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e975e09c8190911e98e6e558615d |
completed | April 20, 2026, 8:53 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.