Triple
T11200842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grande Chartreuse |
E265033
|
entity |
| Predicate | breweryRelation |
P97832
|
FINISHED |
| Object | historically linked to production of Chartreuse liqueur |
—
|
LITERAL 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: historically linked to production of Chartreuse liqueur | Statement: [Grande Chartreuse, breweryRelation, historically linked to production of Chartreuse liqueur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breweryRelation Context triple: [Grande Chartreuse, breweryRelation, historically linked to production of Chartreuse liqueur]
-
A.
breweryType
Indicates the specific category or classification of a brewery based on its operational or business characteristics.
-
B.
beerBrewedBy
Indicates that a particular beer is produced or created by a specific brewer, brewery, or brewing entity.
-
C.
hasBreweryOrFacility
Indicates that an entity possesses, operates, or is associated with a brewery or brewing-related facility.
-
D.
breweryLocation
Indicates the place where a brewery is situated or operates.
-
E.
hasMajorBrewery
Indicates that a location or entity possesses or hosts a large, commercially significant brewery.
- F. None of above. chosen
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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8c36c188190bfa4d5f8e6cbbbea |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69d77062271c8190b63da714ab5beff9 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:29 p.m.