Triple
T37706049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hugh Swynford |
E939199
|
entity |
| Predicate | marriageOrderOfSpouse |
P4764
|
FINISHED |
| Object | first husband of Katherine Swynford |
—
|
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: first husband of Katherine Swynford | Statement: [Hugh Swynford, marriageOrderOfSpouse, first husband of Katherine Swynford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageOrderOfSpouse Context triple: [Hugh Swynford, marriageOrderOfSpouse, first husband of Katherine Swynford]
-
A.
spouseOrder
chosen
Indicates the position or sequence of a person among multiple spouses in a marital relationship.
-
B.
motherSpouseOrder
Indicates that the subject is the spouse of the object’s mother, with an ordering or ranking among multiple such spouses.
-
C.
hasParentMarriageOrder
Indicates the sequential order of a person’s parents’ marriage relative to any other marriages those parents may have had.
-
D.
spouseOfSequence
Indicates a sequential or ordered relationship of being spouses, where each entity is married to the next in the sequence.
-
E.
marriedToRank
Indicates that one entity is married to another entity who holds a specific rank or position.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: May 3, 2026, 4:18 p.m.