Triple
T31109222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emily Cora Gilbert |
E792890
|
entity |
| Predicate | spouseNotableWorkArea |
P22220
|
FINISHED |
| Object | early Hollywood comedies |
—
|
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: early Hollywood comedies | Statement: [Emily Cora Gilbert, spouseNotableWorkArea, early Hollywood comedies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseNotableWorkArea Context triple: [Emily Cora Gilbert, spouseNotableWorkArea, early Hollywood comedies]
-
A.
spouseNotableWorkField
chosen
Indicates that the notable work or professional field associated with a person’s spouse is being specified.
-
B.
spouse notableWork
Indicates that a person's spouse is significantly associated with a particular notable work.
-
C.
spouseNotableFor
Indicates that a person's spouse is recognized or distinguished for a particular achievement, role, or characteristic.
-
D.
spouseNotableWorkLanguage
Indicates that the notable work of a person's spouse is expressed or created in a particular language.
-
E.
spouseNotableWorkPeriod
Indicates the time period during which a spouse created or was associated with their notable work.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: April 29, 2026, 9:04 p.m.