Triple
T12413833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christine Angus |
E296584
|
entity |
| Predicate | spouseActivity |
P55300
|
FINISHED |
| Object | teaching art |
—
|
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: teaching art | Statement: [Christine Angus, spouseActivity, teaching art]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseActivity Context triple: [Christine Angus, spouseActivity, teaching art]
-
A.
spouseAction
Indicates that one person performs an action toward or on their spouse within the context of a marital relationship.
-
B.
spousePoliticalActivity
Indicates that one person’s spouse engages in political actions, involvement, or advocacy connected to that person or their role.
-
C.
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.
-
D.
spouseFamily
Indicates a family relationship formed through marriage, such as between a person and their spouse’s relatives.
-
E.
spouseInvolvedIn
chosen
Indicates that a person's spouse participates in, is associated with, or plays a role in a specified activity, event, or situation.
- 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_69d6ad9f464c81909db36d7e96e34b9e |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e1888b48190bd750f839a26e99e |
completed | April 10, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69d94d354b488190adc83fb4f2770dd5 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.