Triple
T12344402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armstrong-Jones family |
E294311
|
entity |
| Predicate | isLinkedByMarriageTo |
P89337
|
FINISHED |
| Object | British line of succession |
—
|
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: British line of succession | Statement: [Armstrong-Jones family, isLinkedByMarriageTo, British line of succession]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLinkedByMarriageTo Context triple: [Armstrong-Jones family, isLinkedByMarriageTo, British line of succession]
-
A.
connectedThroughMarriageVia
Indicates that two entities are related to each other by a marital connection that is mediated through one or more intermediate spouses or in-laws, rather than by a direct marriage between them.
-
B.
marriedBy
Indicates that one entity is the officiant or authority who performs and formalizes the marriage of another entity.
-
C.
hasMemberSpouseConnection
chosen
Indicates a relationship where one entity is a spouse of a member associated with the other entity.
-
D.
maritalRelations
Indicates a legally or socially recognized spousal relationship or marriage-based connection between two entities.
-
E.
spouseInstanceOf
Indicates that one entity is the specific spouse (marriage partner) instance of another entity.
- F. None of above.
Provenance (3 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f78a970819086beec3e4da8c49e |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ecb5efc819086a3530282278bb1 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.