Triple
T27428317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Londerzeel |
E690552
|
entity |
| Predicate | hasNotableBrewery |
P44058
|
FINISHED |
| Object | Palm Brewery |
—
|
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: Palm Brewery | Statement: [Londerzeel, hasNotableBrewery, Palm Brewery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableBrewery Context triple: [Londerzeel, hasNotableBrewery, Palm Brewery]
-
A.
hasMajorBrewery
chosen
Indicates that a location or entity possesses or hosts a large, commercially significant brewery.
-
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.
hasLocalBrewery
Indicates that a place or region contains at least one brewery that operates locally within its area.
-
D.
hasBreweryOrFacility
Indicates that an entity possesses, operates, or is associated with a brewery or brewing-related facility.
-
E.
hasNotableBeer
Indicates that an entity is associated with a beer that is recognized as distinctive, famous, or otherwise noteworthy.
- 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_69ef52003fb48190b0f1295246182a86 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
Created at: April 27, 2026, 12:41 p.m.