Triple
T35999459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nabeglavi |
E1041087
|
entity |
| Predicate | isProducedAs |
P74478
|
FINISHED |
| Object | commercial bottled beverage |
—
|
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: commercial bottled beverage | Statement: [Nabeglavi, isProducedAs, commercial bottled beverage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isProducedAs Context triple: [Nabeglavi, isProducedAs, commercial bottled beverage]
-
A.
producedAs
chosen
Indicates that one entity is created, generated, or brought into existence as a result or output of another entity or process.
-
B.
isProducedFrom
Indicates that something is created, generated, or derived from a specified source or input.
-
C.
producesFor
Indicates that one entity creates, manufactures, or generates something specifically intended for another entity’s use, benefit, or distribution.
-
D.
originallyProducedAs
Indicates that one entity was first created, released, or manufactured in the form of another specified entity or format.
-
E.
isProducedIn
Indicates that something is created, manufactured, or generated within a particular place, context, or process.
- 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_69f76e29084c819083987b828d414de7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.