Triple
T2717678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angostura bitters |
E60005
|
entity |
| Predicate | typicalServingSize |
P3664
|
FINISHED |
| Object | dashes |
—
|
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: dashes | Statement: [Angostura bitters, typicalServingSize, dashes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalServingSize Context triple: [Angostura bitters, typicalServingSize, dashes]
-
A.
typicalUnitSize
chosen
Indicates the standard or most common size or quantity in which something is typically measured, packaged, or used.
-
B.
BakerYield
Indicates the amount or output produced by a baker, typically in terms of quantity or volume of baked goods resulting from a given process or batch.
-
C.
typicalFlavor
Indicates that something characteristically has or is associated with a particular flavor.
-
D.
servesMostly
Indicates that one entity primarily functions to serve, support, or cater to another entity, more than to any other.
-
E.
typicallyServedAs
Indicates that something is most commonly presented, used, or offered in a particular role, form, or function.
- 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_69ab4b746d248190958e052045c09255 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdaad577c8190819d3c641c2406f4 |
completed | March 7, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69abd8240920819087a812d816a55edb |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.