Triple
T2652267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanukkah gelt |
E53926
|
entity |
| Predicate | usedInGame |
P25490
|
FINISHED |
| Object | dreidel game |
—
|
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: dreidel game | Statement: [Hanukkah gelt, usedInGame, dreidel game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInGame Context triple: [Hanukkah gelt, usedInGame, dreidel game]
-
A.
areUsedIn
chosen
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
B.
playInGameIntroduced
Indicates that an entity participates as a playable element within the specific game in which it was first introduced.
-
C.
usedInBattle
Indicates that something (typically a tool, strategy, or resource) was employed or applied during a battle or combat situation.
-
D.
usedInLeague
Indicates that an entity (such as a team, player, or item) participates or is employed within a particular league.
-
E.
usedAgainst
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
- 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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abda0ba2208190ad87763ecbef8c3c |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd815d06481909535c02b0aba8553 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.