Triple
T34179219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worshipful Company of Upholders |
E876764
|
entity |
| Predicate | awardsPrizes |
P106241
|
FINISHED |
| Object | craftsmanship awards |
—
|
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: craftsmanship awards | Statement: [Worshipful Company of Upholders, awardsPrizes, craftsmanship awards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awardsPrizes Context triple: [Worshipful Company of Upholders, awardsPrizes, craftsmanship awards]
-
A.
awardsAre
chosen
Indicates that one entity confers or grants awards or honors to another entity.
-
B.
isPrizedFor
Indicates that something is highly valued or esteemed because of a particular quality, feature, or benefit it provides.
-
C.
awardIncludes
Indicates that a particular award encompasses, contains, or is composed of the specified component, category, or sub-award.
-
D.
awardsTitle
Indicates that an entity confers or grants a specific title or honorific designation to another entity.
-
E.
alsoAwardedIn
Indicates that the same award or recognition was given in an additional time, place, or context beyond the primary one.
- 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_69f349ae640c8190b9cd220b5368d8b6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: May 1, 2026, 1:54 a.m.