Triple
T35119297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iron Seat |
E1014122
|
entity |
| Predicate | notableClaimant |
P58451
|
FINISHED |
| Object | Stannis Baratheon |
E349979
|
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: Stannis Baratheon | Statement: [Iron Seat, notableClaimant, Stannis Baratheon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableClaimant Context triple: [Iron Seat, notableClaimant, Stannis Baratheon]
-
A.
formerClaimant
Indicates that an entity previously held the status of claimant in a claim or dispute but no longer does so.
-
B.
historicalClaimant
chosen
Indicates that an entity was, at some point in the past, recognized or asserted as having a legitimate claim to another entity (such as a title, position, or resource), regardless of whether that claim is currently valid.
-
C.
modernClaimant
Indicates that an entity is a present-day or contemporary holder or asserter of a particular title, right, or claim.
-
D.
supportedClaimant
Indicates that one entity has provided assistance, backing, or advocacy in favor of another entity who is making a claim or seeking a benefit.
-
E.
claimableBy
Indicates that something is eligible to be claimed, received, or taken by a specified entity.
- F. None of above.
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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a380f9396848190a73091868669bafc |
completed | June 21, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.