Triple
T30766124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arms of the Duke of Hamilton |
E783375
|
entity |
| Predicate | associatedWithSeat |
P207305
|
FINISHED |
| Object | Hamilton Palace (historic family seat) |
E392611
|
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: Hamilton Palace (historic family seat) | Statement: [Arms of the Duke of Hamilton, associatedWithSeat, Hamilton Palace (historic family seat)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSeat Context triple: [Arms of the Duke of Hamilton, associatedWithSeat, Hamilton Palace (historic family seat)]
-
A.
linkedSeat
Indicates that one seat is associated or paired with another seat, such that actions or conditions affecting one may also apply to the other.
-
B.
seatOwnedBy
Indicates that a particular seat is possessed or held in ownership by a specific entity.
-
C.
hasSeatAt
Indicates that an entity occupies or holds a place, position, or membership within a specific group, body, or location.
-
D.
seatOn
Indicates that one entity is positioned or placed on a seat or seating surface associated with another entity.
-
E.
seatAgreementWith
Indicates an arrangement or understanding by which one party provides or allocates seating to another under agreed terms.
- 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_6a28b0963ff08190a8a01f8053df86ec |
completed | June 10, 2026, 12:32 a.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.