Triple
T6477262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arms of the Diocese of Worcester |
E146102
|
entity |
| Predicate | arrangementOfCharges |
P2362
|
FINISHED |
| Object | in pile |
—
|
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: in pile | Statement: [Arms of the Diocese of Worcester, arrangementOfCharges, in pile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arrangementOfCharges Context triple: [Arms of the Diocese of Worcester, arrangementOfCharges, in pile]
-
A.
chargeArrangement
Indicates an agreement or setup specifying how charges, fees, or payments are to be applied or managed between parties.
-
B.
arrangement
chosen
Indicates a relationship where entities are organized, ordered, or positioned in a particular configuration or sequence relative to one another.
-
C.
isArrangementOf
Indicates that one entity is a specific ordering or configuration of the components or elements of another entity.
-
D.
legalCharge
Indicates that an authority has formally accused an entity of committing a specific legal offense or violation.
-
E.
arrangementType
Indicates the specific kind or category of arrangement that characterizes how the related entities are organized or structured in relation to each other.
- 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_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. |
Created at: March 22, 2026, 4:51 p.m.