Triple
T2652276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanukkah gelt |
E53926
|
entity |
| Predicate | oftenWrappedIn |
P7850
|
FINISHED |
| Object | gold foil |
—
|
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: gold foil | Statement: [Hanukkah gelt, oftenWrappedIn, gold foil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenWrappedIn Context triple: [Hanukkah gelt, oftenWrappedIn, gold foil]
-
A.
encodedIn
Indicates that one entity is represented, stored, or expressed within another entity using a specific encoding or format.
-
B.
surrounds
chosen
Indicates that one entity is located all around another entity, enclosing or encircling it on multiple sides or completely.
-
C.
entangledWith
Indicates a mutual state in which two or more entities are so interconnected that a change or condition in one inherently affects or constrains the other(s).
-
D.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
E.
usedInPartOf
Indicates that something is utilized or plays a functional role within a specific component or subpart of a larger whole.
- 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.