Triple
T12940697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moo Brew |
E309627
|
entity |
| Predicate | hasBreweryType |
P53908
|
FINISHED |
| Object | microbrewery |
—
|
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: microbrewery | Statement: [Moo Brew, hasBreweryType, microbrewery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBreweryType Context triple: [Moo Brew, hasBreweryType, microbrewery]
-
A.
breweryType
chosen
Indicates the specific category or classification of a brewery based on its operational or business characteristics.
-
B.
hasBreweryOrFacility
Indicates that an entity possesses, operates, or is associated with a brewery or brewing-related facility.
-
C.
breweryRelation
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).
-
D.
hasIntegratedMicrobrewery
Indicates that an entity includes or contains a microbrewery as a built-in or internal component.
-
E.
hasMajorBrewery
Indicates that a location or entity possesses or hosts a large, commercially significant brewery.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97db69f548190a1a693bc0d6c191a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:43 p.m.