Triple
T562541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Countess of Northesk |
E13483
|
entity |
| Predicate | inheritedOrMarital |
P4942
|
FINISHED |
| Object | marital |
—
|
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: marital | Statement: [Countess of Northesk, inheritedOrMarital, marital]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inheritedOrMarital Context triple: [Countess of Northesk, inheritedOrMarital, marital]
-
A.
marriedInto
chosen
Indicates that one entity became connected to another’s family or group through marriage, rather than by birth or prior membership.
-
B.
marriageType
Indicates the specific legal or social category of a marriage relationship that exists between two spouses.
-
C.
spouseStatus
Indicates the marital relationship status between two individuals, such as whether they are currently spouses, formerly spouses, or not married to each other.
-
D.
spouseOrder
Indicates the position or sequence of a person among multiple spouses in a marital relationship.
-
E.
houseByMarriage
Indicates a familial or household relationship established through marriage rather than by blood or direct residence.
- 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49a700e608190b235246df057bd9b |
completed | March 1, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69a494c044648190a98589ab18935216 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.