Triple
T23626507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cruzcampo |
E583479
|
entity |
| Predicate | hasBrewingFacilityIn |
P77072
|
FINISHED |
| Object | Seville |
—
|
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: Seville | Statement: [Cruzcampo, hasBrewingFacilityIn, Seville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrewingFacilityIn Context triple: [Cruzcampo, hasBrewingFacilityIn, Seville]
-
A.
hasBreweryOrFacility
chosen
Indicates that an entity possesses, operates, or is associated with a brewery or brewing-related facility.
-
B.
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.
-
C.
hasMajorBrewery
Indicates that a location or entity possesses or hosts a large, commercially significant brewery.
-
D.
knownBrewer
Indicates that one entity is recognized as the brewer (producer of beer or similar beverages) associated with another entity.
-
E.
hasCafes
Indicates that one entity possesses, contains, or includes one or more cafes within it.
- 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b17d4f508190abbb508746bfebb9 |
completed | April 29, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:46 p.m.