Triple
T17077145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simply Orange High Pulp |
E414377
|
entity |
| Predicate | containerFeature |
P125775
|
FINISHED |
| Object | resealable cap |
—
|
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: resealable cap | Statement: [Simply Orange High Pulp, containerFeature, resealable cap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containerFeature Context triple: [Simply Orange High Pulp, containerFeature, resealable cap]
-
A.
containerType
Indicates the specific kind or category of container associated with or used to hold an entity.
-
B.
integrationFeature
Indicates that one entity provides a capability or component specifically intended to enable or support integration with another system, service, or component.
-
C.
withinFeature
Indicates that one entity is spatially contained inside or lies entirely within the bounds of another feature.
-
D.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
E.
throughFeature
Indicates that one entity is connected to, accessed, or achieved by means of a particular feature or characteristic of another entity.
- F. None of above. chosen
Provenance (4 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc559388190b685504cca6ed62b |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:34 a.m.