Triple
T28247504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoppin John |
E712206
|
entity |
| Predicate | isCustomarilyPreparedOn |
P102145
|
FINISHED |
| Object | New Year’s Eve |
—
|
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: New Year’s Eve | Statement: [Hoppin John, isCustomarilyPreparedOn, New Year’s Eve]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCustomarilyPreparedOn Context triple: [Hoppin John, isCustomarilyPreparedOn, New Year’s Eve]
-
A.
commonlyPreparedFor
chosen
Indicates that something is typically made, organized, or arranged in anticipation of a particular event, purpose, or recipient.
-
B.
typicalPreparation
Indicates the usual or standard way in which something is prepared or made.
-
C.
preparationBy
Indicates that one entity is created, assembled, or made ready through the actions or processes performed by another entity.
-
D.
traditionalPreparation
Indicates that something is prepared or made using customary, long-established methods or techniques associated with a particular culture or practice.
-
E.
isCookedBy
Indicates that something has been prepared or made ready for eating through cooking by a particular agent.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f643ca9bb081909a9057a8d2623465 |
completed | May 2, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 11:02 p.m.