Triple
T35976165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Cruise of the Janet Nichol (as editor/diarist) |
E1040422
|
entity |
| Predicate | diarist |
P184301
|
FINISHED |
| Object | Fanny Van de Grift Osbourne |
—
|
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: Fanny Van de Grift Osbourne | Statement: [The Cruise of the Janet Nichol (as editor/diarist), diarist, Fanny Van de Grift Osbourne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diarist Context triple: [The Cruise of the Janet Nichol (as editor/diarist), diarist, Fanny Van de Grift Osbourne]
-
A.
diaryWrittenIn
Indicates that a diary is composed or recorded using a particular language or writing system.
-
B.
poet
Indicates that an entity creates poetry or is recognized for engaging in the activity of writing poems.
-
C.
reporter
Indicates that an entity acts in the role of a reporter, typically gathering, writing, or presenting information or news about another entity or event.
-
D.
diaryLocation
Indicates the place where a diary is kept, stored, or situated.
-
E.
journalingType
Indicates the specific method or format used when someone engages in journaling.
- 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_69f76e27758c81909b711cf38a130aaf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ad15f3b88190b7c9742a734fec5f |
completed | May 3, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7acad20388190b9b10270ca9bdfbc |
completed | May 3, 2026, 8:14 p.m. |
Created at: May 3, 2026, 4:07 p.m.