Triple
T6181316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arms of the Diocese of Derby |
E137947
|
entity |
| Predicate | borderCharge |
P38214
|
FINISHED |
| Object | red roses |
—
|
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: red roses | Statement: [Arms of the Diocese of Derby, borderCharge, red roses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCharge Context triple: [Arms of the Diocese of Derby, borderCharge, red roses]
-
A.
centralCharge
Indicates that an entity has a specific central charge value, typically quantifying a key parameter in a conformal or related physical or mathematical theory.
-
B.
crestAdditionalCharge
Indicates an extra fee or surcharge applied in addition to a base cost, typically associated with a specific crest-related service or item.
-
C.
chargeOnChief
Indicates that a formal accusation or legal charge is filed against a chief or primary authority figure.
-
D.
chargesVia
Indicates that one entity charges or powers another entity using a specified medium, method, or interface.
-
E.
borderCharacteristic
chosen
Indicates that one entity specifies a property, feature, or quality of the border or boundary 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c060fdf7ac8190a0e887907ec9a922 |
completed | March 22, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:18 p.m.