Triple
T33003640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worshipful Company of Plumbers |
E844436
|
entity |
| Predicate | tradeRepresented |
P154478
|
FINISHED |
| Object | plumbing |
—
|
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: plumbing | Statement: [Worshipful Company of Plumbers, tradeRepresented, plumbing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradeRepresented Context triple: [Worshipful Company of Plumbers, tradeRepresented, plumbing]
-
A.
tradeAspect
Indicates a relationship where one entity is associated with a specific aspect, feature, or dimension of a trade or commercial transaction.
-
B.
originallyRepresentedTrade
chosen
Indicates that something was initially created or used to symbolize, depict, or stand for a particular trade, profession, or commercial activity.
-
C.
tradeNetwork
Indicates a relationship where entities are connected through the exchange of goods, services, or resources within an ongoing system of trade.
-
D.
tradeHubWith
Indicates that one entity functions as a central location or node for trading activities in connection with another entity.
-
E.
tradesAs
Indicates that one entity conducts business or is publicly known under the trading name or brand of another entity.
- 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:23 a.m.