Triple
T26828028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morwen Eledhwen |
E675421
|
entity |
| Predicate | husbandStatus |
P161517
|
FINISHED |
| Object | Húrin was captured by Morgoth |
—
|
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: Húrin was captured by Morgoth | Statement: [Morwen Eledhwen, husbandStatus, Húrin was captured by Morgoth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: husbandStatus Context triple: [Morwen Eledhwen, husbandStatus, Húrin was captured by Morgoth]
-
A.
spouseStatus
Indicates the marital relationship status between two individuals, such as whether they are currently spouses, formerly spouses, or not married to each other.
-
B.
marital status
Indicates the legal or social state of a person’s marriage-related relationship, such as being single, married, divorced, or widowed.
-
C.
spouseStatusAtMarriage
Indicates the marital status each partner held at the time their marriage to one another was formed.
-
D.
spouseWealthStatus
Indicates the financial status or wealth level of a person’s spouse in relation to that person.
-
E.
spouseState
Indicates the marital status or condition of a person’s spouse in relation to them.
- F. None of above. chosen
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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61ada00d48190b6f4c52e6bd33789 |
completed | May 2, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6142a0b988190b404d078f73c3cb9 |
completed | May 2, 2026, 3:11 p.m. |
Created at: April 27, 2026, 4:59 a.m.