Triple
T22277892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emily Temple, Viscountess Palmerston |
E550652
|
entity |
| Predicate | roleInHusbandsCareer |
P103820
|
FINISHED |
| Object | supporting political networking |
—
|
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: supporting political networking | Statement: [Emily Temple, Viscountess Palmerston, roleInHusbandsCareer, supporting political networking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInHusbandsCareer Context triple: [Emily Temple, Viscountess Palmerston, roleInHusbandsCareer, supporting political networking]
-
A.
roleInSpouseCareer
chosen
Indicates the nature or extent of a person’s involvement or influence in their spouse’s professional career.
-
B.
spouseOccupation
Indicates that one person’s spouse has a particular job, profession, or occupation.
-
C.
spouseIndustry
Indicates the industry or sector in which a person's spouse is employed or primarily involved.
-
D.
spouseInWork
Indicates that two entities are spouses within the context of a particular work (such as a book, film, or series), rather than in real life.
-
E.
afterMarriageRole
Indicates the role or status an entity assumes following a marriage event.
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f14ea96948819081c1ae6c7b11ab62 |
completed | April 29, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.