Triple
T24308731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosie M. Banks |
E612606
|
entity |
| Predicate | writingStyleInUniverse |
P125577
|
FINISHED |
| Object | sentimental |
—
|
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: sentimental | Statement: [Rosie M. Banks, writingStyleInUniverse, sentimental]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingStyleInUniverse Context triple: [Rosie M. Banks, writingStyleInUniverse, sentimental]
-
A.
typicalStyleInFiction
chosen
Indicates the characteristic narrative or artistic style that an entity most commonly exhibits within fictional works.
-
B.
writesInStyle
Indicates that an entity creates written work using a particular style or manner of writing.
-
C.
literaryUniverse
Indicates that two or more works of literature exist within the same fictional universe or continuity, sharing settings, characters, or canonical events.
-
D.
narrativeStyle
Indicates how a narrative is told, such as the point of view, tone, and structural approach used to present a story or account.
-
E.
fictionalUniverse
Indicates that two entities exist within, or are associated with, the same fictional universe or narrative setting.
- 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29228ede48190b05c85320f373155 |
completed | April 29, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:32 a.m.