Triple
T37675268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arms of Russell, Dukes of Bedford |
E938074
|
entity |
| Predicate | supporterCharge |
P204336
|
FINISHED |
| Object | goat rampant |
—
|
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: goat rampant | Statement: [Arms of Russell, Dukes of Bedford, supporterCharge, goat rampant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supporterCharge Context triple: [Arms of Russell, Dukes of Bedford, supporterCharge, goat rampant]
-
A.
supporterType
Indicates the specific role or category of support a supporter provides in relation to another entity or activity.
-
B.
supporterFeatures
Indicates that one entity provides supporting characteristics, capabilities, or functionalities that enhance or enable another entity.
-
C.
supporter
Indicates a relationship where one entity backs, advocates for, or provides assistance to another entity, often in an ongoing or affiliative way.
-
D.
supporterOf
Indicates that one entity backs, advocates for, or provides assistance to another entity, cause, or organization.
-
E.
supportersShieldRunnerUp
Indicates that an entity finished as the runner-up in a competition or event called the Supporters Shield.
- 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_69f76ed7b1408190ba8c93c53cb8becf |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:18 p.m.