Triple
T26508182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Bull Orange Edition |
E669607
|
entity |
| Predicate | sharesFormulaBaseWith |
P45217
|
FINISHED |
| Object | Red Bull Energy Drink |
—
|
NE NERFINISHED |
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: Red Bull Energy Drink | Statement: [Red Bull Orange Edition, sharesFormulaBaseWith, Red Bull Energy Drink]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesFormulaBaseWith Context triple: [Red Bull Orange Edition, sharesFormulaBaseWith, Red Bull Energy Drink]
-
A.
sharesBaseWith
chosen
Indicates that two entities have a common underlying base element, source, or component from which they are derived or constructed.
-
B.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
C.
sharesForm
Indicates that two entities have the same structural or morphological form.
-
D.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
-
E.
sharesNameWith
Indicates that two entities have the same name or an identical naming designation.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 27, 2026, 1:18 a.m.