Triple
T28008282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budweiser Budvar Brewery |
E707342
|
entity |
| Predicate | basedOnPlaceName |
P99755
|
FINISHED |
| Object | Budweis |
E707352
|
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: Budweis | Statement: [Budweiser Budvar Brewery, basedOnPlaceName, Budweis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnPlaceName Context triple: [Budweiser Budvar Brewery, basedOnPlaceName, Budweis]
-
A.
hasPlaceNamesIn
Indicates that something contains, references, or is associated with one or more place names within it.
-
B.
hasPlaceNamesakeIn
chosen
Indicates that something is named after a particular place or location.
-
C.
isToponymIn
Indicates that a place name (toponym) is located within or refers to a specific geographic area or region.
-
D.
isToponymOf
Indicates that one entity is a place name (toponym) that refers to the location represented by the other entity.
-
E.
hasNotableToponym
Indicates that an entity is associated with a place name that is particularly notable, distinctive, or significant.
- F. None of above.
Provenance (4 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a15b89cf624819086c0a0f34a6b0756 |
completed | May 26, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 27, 2026, 8:02 p.m.