Triple
T4290594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henrietta Rothschild |
E97378
|
entity |
| Predicate | associatedWithFieldThroughSpouse |
P55242
|
FINISHED |
| Object | anthropology |
—
|
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: anthropology | Statement: [Henrietta Rothschild, associatedWithFieldThroughSpouse, anthropology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFieldThroughSpouse Context triple: [Henrietta Rothschild, associatedWithFieldThroughSpouse, anthropology]
-
A.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
B.
spouseMemberOf
Indicates that a person’s spouse is a member of a specified group, organization, or entity.
-
C.
spouseInstanceOf
Indicates that one entity is the specific spouse (marriage partner) instance of another entity.
-
D.
spouseFamily
Indicates a family relationship formed through marriage, such as between a person and their spouse’s relatives.
-
E.
spouseType
Indicates the specific role or category of a person within a spousal relationship (e.g., husband, wife, partner).
- 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_69b3454595848190a0e6bbb6a2bea040 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3507efb28819091a9d5b9161a5008 |
completed | March 12, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69b347fc4c0c8190a7fcd814e27308a5 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e0606488190baadf469a1afc3c2 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:08 p.m.