Triple
T22517568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larue Beer |
E556687
|
entity |
| Predicate | servingContainer |
P72115
|
FINISHED |
| Object | bottle |
—
|
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: bottle | Statement: [Larue Beer, servingContainer, bottle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servingContainer Context triple: [Larue Beer, servingContainer, bottle]
-
A.
servingVessel
chosen
Indicates that one entity functions as the container or vessel used to serve another entity (such as food or drink).
-
B.
servesWith
Indicates that one entity is customarily presented, used, or consumed together with another as a complementary accompaniment.
-
C.
servesVessels
Indicates that one entity provides or supplies vessels (such as containers, ships, or similar items) for the use or benefit of another entity.
-
D.
isServedOn
Indicates that one item (typically food or drink) is presented or provided atop or together with a particular surface, container, or accompaniment.
-
E.
servedWith
Indicates that one item is customarily presented, provided, or consumed together with another as an accompaniment or side.
- 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_69e11e5657e881909f16ca58352c50da |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15e2f5c308190a0e6755a24340917 |
completed | April 29, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:50 p.m.