Triple
T32571545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lothíriel |
E832527
|
entity |
| Predicate | notableRelativesByMarriage |
P29616
|
FINISHED |
| Object | Théoden |
E242439
|
NE 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: Théoden | Statement: [Lothíriel, notableRelativesByMarriage, Théoden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRelativesByMarriage Context triple: [Lothíriel, notableRelativesByMarriage, Théoden]
-
A.
spouseNotableAncestor
Indicates that a person’s spouse has an ancestor who is notable or historically significant.
-
B.
marriedToNotablePerson
chosen
Indicates that a person is legally married to another individual who is widely recognized or notable.
-
C.
spouseNotableFor
Indicates that a person's spouse is recognized or distinguished for a particular achievement, role, or characteristic.
-
D.
spouseFatherInLawNotableFor
Indicates that a person’s spouse’s father (their father-in-law) is notable or distinguished for a particular achievement, role, or characteristic.
-
E.
familyNotableMember
Indicates that a particular individual is a distinguished or noteworthy member of a given family.
- F. None of above.
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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a35813113908190ad02a2b9a6e4b39e |
completed | June 19, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:03 a.m.