Triple
T25524554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thums Up |
E639741
|
entity |
| Predicate | wasOriginallyLaunchedBy |
P5599
|
FINISHED |
| Object | Parle Agro |
—
|
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: Parle Agro | Statement: [Thums Up, wasOriginallyLaunchedBy, Parle Agro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasOriginallyLaunchedBy Context triple: [Thums Up, wasOriginallyLaunchedBy, Parle Agro]
-
A.
wasOriginallyDevelopedBy
Indicates that something (such as a concept, product, or system) was first created or developed by a particular agent or entity.
-
B.
formerlyDevelopedBy
Indicates that an entity was developed in the past by another entity, but is no longer developed by that same party.
-
C.
wasFirstCommercializedBy
Indicates that the subject was initially brought to market or made commercially available by the object.
-
D.
firstAnnouncedBy
Indicates that one entity is the original source or originator that publicly disclosed, reported, or made known another entity or item for the first time.
-
E.
parentCompanyAtLaunch
chosen
Indicates that one company was the owning or controlling parent company of another entity at the time that entity was launched.
- 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f85e975c8190bdadf34f099f3614 |
completed | May 2, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 3:09 p.m.