Triple
T36508929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castle Lager |
E899845
|
entity |
| Predicate | brandFamily |
P11218
|
FINISHED |
| Object |
Castle brand
Castle brand is a prominent South African beer brand family best known for its flagship Castle Lager and its long-standing presence in the country’s brewing industry.
|
E2187443
|
NE 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: Castle brand | Statement: [Castle Lager, brandFamily, Castle brand]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Castle brand Triple: [Castle Lager, brandFamily, Castle brand]
Generated description
Castle brand is a prominent South African beer brand family best known for its flagship Castle Lager and its long-standing presence in the country’s brewing industry.
Provenance (5 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c1ecbf748190aeec443850a78c61 |
completed | May 3, 2026, 9:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39dbd719d4819085afb3e327f3a849 |
completed | June 23, 2026, 1:05 a.m. |
| NEDg | Description generation | batch_6a39dd8014508190a5812e3a48753089 |
completed | June 23, 2026, 1:12 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a39e07b0c80819094800f50088982ce |
completed | June 23, 2026, 1:25 a.m. |
Created at: May 3, 2026, 4:10 p.m.