Triple
T3045703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuremberg gingerbread |
E83440
|
entity |
| Predicate | isPackagedAs |
P9900
|
FINISHED |
| Object | gift tins |
—
|
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: gift tins | Statement: [Nuremberg gingerbread, isPackagedAs, gift tins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPackagedAs Context triple: [Nuremberg gingerbread, isPackagedAs, gift tins]
-
A.
isDeployedFrom
Indicates that one entity originates, is launched, or put into operation from another specified source or location.
-
B.
hasPackageSystem
Indicates that an entity uses or is associated with a particular package management system for installing, updating, or managing software components.
-
C.
alsoDefinedInPackage
Indicates that the same element or concept is additionally defined or declared in another software package.
-
D.
isPartOfFramework
Indicates that one entity functions as a component, module, or element within a larger structured framework or system.
-
E.
packaging
chosen
Indicates that one entity serves as the container, wrapper, or enclosing material used to package 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_69ad8b24924c8190a9bb6f61d519e4ae |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9bab541c8190a17aca26b3dcfae7 |
completed | March 8, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69ad961fc62c819087c4c3a44b00847d |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.