Triple
T524391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diary |
E10885
|
entity |
| Predicate | hasNarrativePerspective |
P1924
|
FINISHED |
| Object | first-person |
—
|
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 | Statement: [Diary, hasNarrativePerspective, first-person]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNarrativePerspective Context triple: [Diary, hasNarrativePerspective, first-person]
-
A.
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.
-
B.
hasNarrative
Indicates that one entity contains, presents, or is associated with a story or narrative about another entity or subject.
-
C.
containsNarrativeOf
Indicates that one entity includes or presents the story, account, or narrative content of another entity.
-
D.
narrativeFrame
Indicates the overarching narrative context or perspective within which events, actions, or relationships are presented or interpreted.
-
E.
perspectiveOf
Indicates that something is expressed, depicted, or understood from the viewpoint or standpoint of a particular entity.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1b656c08190b387f21b06d99e68 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f018129c81909494450fcba71b59 |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.