Triple
T24943896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carol Fox Fuhrman |
E624132
|
entity |
| Predicate | spouseOfPublisherOf |
P157264
|
FINISHED |
| Object | The New York Times |
—
|
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: The New York Times | Statement: [Carol Fox Fuhrman, spouseOfPublisherOf, The New York Times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseOfPublisherOf Context triple: [Carol Fox Fuhrman, spouseOfPublisherOf, The New York Times]
-
A.
spouseOfCreatorOf
Indicates that one entity is the spouse of the person who created another entity.
-
B.
spouseOfFounderOf
Indicates that one entity is the spouse of another entity who is the founder of a specified organization or entity.
-
C.
hasAuthorSpouse
Indicates that the spouse of the subject entity is the author of the related work or entity.
-
D.
spouseOfFounder
Indicates that one entity is the spouse (married partner) of the founder of another entity.
-
E.
designerSpouseOf
Indicates that one person is the spouse of another and works professionally as a designer.
- 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f423dd366081908c3cf86c20c7ec5f |
completed | May 1, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f423637bec8190a1701421ac86a3b7 |
completed | May 1, 2026, 3:52 a.m. |
Created at: April 18, 2026, 5:52 a.m.