Triple
T38569050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Lothlórien |
E928310
|
entity |
| Predicate | spouseOfHolder |
P121785
|
FINISHED |
| Object | Galadriel |
—
|
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: Galadriel | Statement: [Lord of Lothlórien, spouseOfHolder, Galadriel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseOfHolder Context triple: [Lord of Lothlórien, spouseOfHolder, Galadriel]
-
A.
firstHolderSpouseOf
Indicates that the first holder in the relation is the spouse (married partner) of the other holder.
-
B.
spouseOfHead
Indicates that one person is the married partner of the individual who holds the position of head (e.g., head of a household, organization, or state).
-
C.
thirdHolderSpouse
Indicates that the spouse of the third holder in a sequence or group is related to another specified entity.
-
D.
spouseOfWork
Indicates that one person is the spouse of another specifically in the context of their workplace or professional environment.
-
E.
spouseMember
chosen
Indicates that one entity is the spouse (married partner) of another entity.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fedec693b08190b0f8bfdb921e0766 |
completed | May 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69fede16c1d48190a20d8a9c5722c307 |
completed | May 9, 2026, 7:11 a.m. |
Created at: May 3, 2026, 4:32 p.m.