Triple
T29741711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles III of Scotland |
E752624
|
entity |
| Predicate | relatedClaimantTitle |
P5052
|
FINISHED |
| Object | James III and VIII |
E303847
|
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: James III and VIII | Statement: [Charles III of Scotland, relatedClaimantTitle, James III and VIII]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedClaimantTitle Context triple: [Charles III of Scotland, relatedClaimantTitle, James III and VIII]
-
A.
relatedTitleHolder
Indicates that one entity holds a title or position that is related or connected to the title or position held by another entity.
-
B.
claimedTitle
chosen
Indicates that an entity asserts or declares possession of a particular title or rank.
-
C.
relatedToClaimOf
Indicates a relationship where something is connected or pertinent to a specific claim or assertion.
-
D.
associatedTitle
Indicates that one entity has a title, designation, or formal label that is linked or relevant to another entity.
-
E.
relatedTitleOfBearer
Indicates that one title is related to another title held by the same bearer, expressing an associative or contextual connection between those titles.
- 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_69f0d62b064081908c1ae61cd68fb139 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a01a9e333fc819087d583ff319be0b3 |
completed | May 11, 2026, 10:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a26c8e6fa5c81908c63cc4350978226 |
completed | June 8, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_6a01a877c9e08190b0678618d3533286 |
completed | May 11, 2026, 9:59 a.m. |
Created at: April 28, 2026, 7:48 p.m.