Triple
T33950645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchess of Finland |
E870429
|
entity |
| Predicate | hasSpouseOfHolder |
P17782
|
FINISHED |
| Object | John III of Sweden |
—
|
NE NERFINISHED |
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: John III of Sweden | Statement: [Duchess of Finland, hasSpouseOfHolder, John III of Sweden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpouseOfHolder Context triple: [Duchess of Finland, hasSpouseOfHolder, John III of Sweden]
-
A.
spouseSignatoryOf
Indicates that a person is the spouse of another person who has signed a document or agreement, emphasizing the marital relationship to the signatory.
-
B.
firstHolderSpouseOf
chosen
Indicates that the first holder in the relation is the spouse (married partner) of the other holder.
-
C.
thirdHolderSpouse
Indicates that the spouse of the third holder in a sequence or group is related to another specified entity.
-
D.
secondHolderSpouse
Indicates that the second holder in a given context is married to the referenced spouse.
-
E.
spouseTermCoincidesWith
Indicates that the term used to refer to a spouse coincides exactly with another specified term in form or usage.
- 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_69f3499c2d7481909c953a5010227725 |
completed | April 30, 2026, 12:22 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 1, 2026, 1:49 a.m.