Triple
T36919850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fisher Bloom |
E913153
|
entity |
| Predicate | settingTimeOfWorkAppearsIn |
P32393
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Fisher Bloom, settingTimeOfWorkAppearsIn, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingTimeOfWorkAppearsIn Context triple: [Fisher Bloom, settingTimeOfWorkAppearsIn, late 19th century]
-
A.
workSettingPeriod
chosen
Indicates the time period during which a particular work setting or employment context is in effect.
-
B.
timeSlotOfWorks
Indicates the specific time period or interval during which the works (e.g., tasks, events, or activities) are scheduled or take place.
-
C.
appearsInWorkRange
Indicates that an entity is featured or occurs within a specified range or subset of a larger work or collection of works.
-
D.
settingOfWorkAppearsIn
Indicates that a particular place, time, or environment serves as the setting within which a given creative work’s events or narrative occur.
-
E.
timePeriodOfWorks
Indicates the span of time during which the associated works were created, produced, or active.
- 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: May 3, 2026, 4:13 p.m.