Triple
T6477263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arms of the Diocese of Worcester |
E146102
|
entity |
| Predicate | shapeOfCharges |
P71133
|
FINISHED |
| Object | bezants |
—
|
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: bezants | Statement: [Arms of the Diocese of Worcester, shapeOfCharges, bezants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shapeOfCharges Context triple: [Arms of the Diocese of Worcester, shapeOfCharges, bezants]
-
A.
centralChargeDepicts
Indicates that the central charge of an object or system visually represents or symbolically depicts another entity or concept.
-
B.
hasBillShape
Indicates that one entity has a bill whose shape matches the specified form or category.
-
C.
colorCharge
Indicates a relationship where an entity possesses a specific quantum color charge (such as red, green, or blue) in the context of strong nuclear interactions.
-
D.
chargeArrangement
Indicates an agreement or setup specifying how charges, fees, or payments are to be applied or managed between parties.
-
E.
numberOfCharges
Indicates the count of distinct charges, accusations, or fee items associated with an entity or event.
- 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_69c008fec7408190af7b146dc63d9750 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a4ba9588190a965b9e7feb7e598 |
completed | March 22, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69c0673f6d48819080e10c85155c7195 |
completed | March 22, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69c06822f73081908e6bb9edecbe77a6 |
completed | March 22, 2026, 10:07 p.m. |
Created at: March 22, 2026, 4:51 p.m.