Triple
T14484394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Rank |
E359189
|
entity |
| Predicate | relationshipToTorvald |
P114389
|
FINISHED |
| Object | Torvald Helmer’s friend |
—
|
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: Torvald Helmer’s friend | Statement: [Dr. Rank, relationshipToTorvald, Torvald Helmer’s friend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToTorvald Context triple: [Dr. Rank, relationshipToTorvald, Torvald Helmer’s friend]
-
A.
emotionTowardsWife
Indicates that a person experiences or expresses a particular emotion directed toward their wife.
-
B.
describedBySpouseAs
Indicates that one person is characterized, portrayed, or referred to in a particular way by their spouse.
-
C.
relationshipWithHumbertHumbert
Indicates that an entity has a specified type of personal, emotional, or social relationship with Humbert Humbert.
-
D.
spouseRelationshipContext
Indicates a marital relationship context between two entities, specifying that they are spouses or partners in a recognized marriage-like union.
-
E.
sonInLaw
Indicates that one person is the husband of another person's child.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de924d7f4c8190b1f62b5ffe1ff649 |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:20 a.m.