Triple
T17077110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simply Orange Medium Pulp |
E414376
|
entity |
| Predicate | intendedServing |
P86310
|
FINISHED |
| Object | single-serve |
—
|
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: single-serve | Statement: [Simply Orange Medium Pulp, intendedServing, single-serve]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedServing Context triple: [Simply Orange Medium Pulp, intendedServing, single-serve]
-
A.
intendedToServe
Indicates that one entity was designed, planned, or purposed specifically to benefit, assist, or fulfill the needs of another entity.
-
B.
isServedFor
chosen
Indicates that something is provided or presented as suitable or intended for a particular purpose, use, or recipient.
-
C.
aimsToServeAs
Indicates that one entity has the intention or purpose of functioning in the role or capacity of another entity.
-
D.
isServed
Indicates that one entity provides or delivers a service, product, or assistance to another entity.
-
E.
isServedOn
Indicates that one item (typically food or drink) is presented or provided atop or together with a particular surface, container, or accompaniment.
- 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_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. |
Created at: April 10, 2026, 5:34 a.m.