Triple
T18516498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emily Pepys |
E452477
|
entity |
| Predicate | diaryPerspective |
P1924
|
FINISHED |
| Object | first-person narrative |
—
|
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: first-person narrative | Statement: [Emily Pepys, diaryPerspective, first-person narrative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diaryPerspective Context triple: [Emily Pepys, diaryPerspective, first-person narrative]
-
A.
journalingType
Indicates the specific method or format used when someone engages in journaling.
-
B.
spouseDiaryNote
Indicates that one person has written a diary note or entry specifically about their spouse or marital relationship.
-
C.
perspectiveOf
Indicates that something is expressed, depicted, or understood from the viewpoint or standpoint of a particular entity.
-
D.
narrativePerspective
chosen
Indicates the point of view or vantage from which a narrative is told, specifying the relationship between the storyteller and the events being described.
-
E.
useOfPerspective
Indicates that one entity adopts or applies a particular visual, narrative, or conceptual viewpoint in relation to another entity or context.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5338a628c81909db08ae7dc94f59a |
completed | April 19, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.