Triple
T26389478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krating Daeng |
E663373
|
entity |
| Predicate | originalFormulaFor |
P2310
|
FINISHED |
| Object | Red Bull |
—
|
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 | Statement: [Krating Daeng, originalFormulaFor, Red Bull]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalFormulaFor Context triple: [Krating Daeng, originalFormulaFor, Red Bull]
-
A.
primaryFormulaFormat
Indicates the main or default structural format in which a formula is represented or stored.
-
B.
formulaUsed
Indicates that a particular formula is employed or applied in performing a calculation, derivation, or reasoning step.
-
C.
recitesFormula
Indicates that one entity verbally or mentally repeats a specific formula, such as a set phrase, equation, or ritual wording, typically from memory.
-
D.
formulaInvolves
Indicates that a given formula includes, references, or depends on a specified element or component.
-
E.
keyFormula
chosen
Indicates that a formula serves as the primary or defining expression associated with an entity or relationship.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 26, 2026, 11:24 p.m.