Triple
T30766115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arms of the Duke of Hamilton |
E783375
|
entity |
| Predicate | supportersBelongTo |
P207304
|
FINISHED |
| Object | Duke of Hamilton |
E22218
|
NE 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: Duke of Hamilton | Statement: [Arms of the Duke of Hamilton, supportersBelongTo, Duke of Hamilton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportersBelongTo Context triple: [Arms of the Duke of Hamilton, supportersBelongTo, Duke of Hamilton]
-
A.
supporterOf
Indicates that one entity backs, advocates for, or provides assistance to another entity, cause, or organization.
-
B.
supportersGroupType
Indicates the classification or category of a supporters group associated with an entity.
-
C.
supporters
Indicates a relationship where one entity backs, endorses, or actively helps another entity, cause, or position.
-
D.
refersToClubSupporterGroup
Indicates that an entity is associated with or designates a specific club supporter group.
-
E.
supporterIdentity
Indicates that one entity is identified as a supporter (e.g., backer, advocate, or sponsor) of another entity or cause.
- F. None of above. chosen
Provenance (5 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_69f224b047f48190b4f5efeb7ee97b37 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3692b65d1c8190b6940e41c91cdd06 |
completed | June 20, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 8:40 p.m.