Triple
T26059025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | yemas de Santa Teresa |
E657204
|
entity |
| Predicate | isUsuallyPackagedIn |
P90629
|
FINISHED |
| Object | small boxes |
—
|
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: small boxes | Statement: [yemas de Santa Teresa, isUsuallyPackagedIn, small boxes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsuallyPackagedIn Context triple: [yemas de Santa Teresa, isUsuallyPackagedIn, small boxes]
-
A.
packagingIncludes
Indicates that the packaging of one item contains or comes with another specified item or component.
-
B.
typicalPackage
chosen
Indicates that something is the standard or commonly used package associated with a given entity or context.
-
C.
isPackagedFor
Indicates that one entity is prepared, contained, or wrapped specifically for use, sale, or distribution in connection with another entity.
-
D.
packaging
Indicates that one entity serves as the container, wrapper, or enclosing material used to package another entity.
-
E.
packagingRequirement
Indicates the specific conditions, standards, or constraints that must be met in how something is packaged.
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60690f0d88190a7b68c209439bf64 |
completed | May 2, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 7:14 p.m.