Triple
T34237781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pop-Tarts |
E878379
|
entity |
| Predicate | servingConfiguration |
P193079
|
FINISHED |
| Object | two pastries per pouch |
—
|
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: two pastries per pouch | Statement: [Pop-Tarts, servingConfiguration, two pastries per pouch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servingConfiguration Context triple: [Pop-Tarts, servingConfiguration, two pastries per pouch]
-
A.
servesMode
Indicates that one entity provides or operates in a particular manner, method, or mode in relation to another entity or context.
-
B.
servedFrom
Indicates that something is provided, delivered, or made available from a particular source or location.
-
C.
servingRule
Indicates that one entity specifies or enforces the rules or conditions under which another entity is served or provided.
-
D.
servesFeature
Indicates that one entity provides or makes available a particular feature or functionality to another entity.
-
E.
servedSystem
Indicates that one system has provided service, functionality, or resources to another system.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69fd37b45b4481908b947b52fbcb7ade |
completed | May 8, 2026, 1:09 a.m. |
Created at: May 1, 2026, 1:56 a.m.