Triple
T27635964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Modelo |
E696468
|
entity |
| Predicate | associatedWithBrewery |
P97832
|
FINISHED |
| Object | Grupo Modelo |
—
|
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: Grupo Modelo | Statement: [Modelo, associatedWithBrewery, Grupo Modelo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithBrewery Context triple: [Modelo, associatedWithBrewery, Grupo Modelo]
-
A.
breweryRelation
chosen
Indicates a relationship in which one entity is a brewery associated with, producing for, or otherwise linked to another entity (such as a brand, product, or location).
-
B.
beerBrewedBy
Indicates that a particular beer is produced or created by a specific brewer, brewery, or brewing entity.
-
C.
knownBrewer
Indicates that one entity is recognized as the brewer (producer of beer or similar beverages) associated with another entity.
-
D.
hasBreweryFocus
Indicates that an entity (such as a business, product, or activity) is primarily oriented around, specialized in, or dedicated to breweries or brewing-related operations.
-
E.
breweryType
Indicates the specific category or classification of a brewery based on its operational or business characteristics.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_6a00315632a8819092290f455babd7ee |
completed | May 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_6a002f54a0dc81909b0e54c5e110e67c |
completed | May 10, 2026, 7:10 a.m. |
Created at: April 27, 2026, 2:23 p.m.