Triple
T33023391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worshipful Company of Brewers |
E844972
|
entity |
| Predicate | representsTrade |
P198267
|
FINISHED |
| Object | brewing |
—
|
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: brewing | Statement: [Worshipful Company of Brewers, representsTrade, brewing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsTrade Context triple: [Worshipful Company of Brewers, representsTrade, brewing]
-
A.
originallyRepresentedTrade
Indicates that something was initially created or used to symbolize, depict, or stand for a particular trade, profession, or commercial activity.
-
B.
tradesAs
Indicates that one entity conducts business or is publicly known under the trading name or brand of another entity.
-
C.
tradeInvolves
Indicates that a trade or exchange relationship exists between the referenced entities, where goods, services, or value are transferred among them.
-
D.
isTradedBy
Indicates that an item, asset, or resource is exchanged or dealt with by a particular agent, party, or trading entity.
-
E.
tradedUsing
Indicates that an exchange or trade was conducted by means of a specified instrument, medium, or mechanism.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fed6da0390819096b88ef4714b144e |
completed | May 9, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69fed53517d081909966f31707625f1a |
completed | May 9, 2026, 6:33 a.m. |
| PDg | Predicate description generation | batch_69fed6d90f2081909cd21e5e973a6b89 |
completed | May 9, 2026, 6:40 a.m. |
Created at: May 1, 2026, 1:23 a.m.