Triple
T36875299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miss Tina |
E911326
|
entity |
| Predicate | literaryPeriodOfOrigin |
P173252
|
FINISHED |
| Object | late 19th century literature |
—
|
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 literature | Statement: [Miss Tina, literaryPeriodOfOrigin, late 19th century literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literaryPeriodOfOrigin Context triple: [Miss Tina, literaryPeriodOfOrigin, late 19th century literature]
-
A.
literaryPeriodOfSubject
chosen
Indicates the literary period or movement with which the subject is associated.
-
B.
literaryPeriodOfWork
Indicates the literary period or movement to which a particular work belongs.
-
C.
literaryPeriodOfReception
Indicates the historical literary period during which a work was primarily received, interpreted, or influential.
-
D.
literaryMovementReception
Indicates how a particular literary movement has been received, interpreted, or evaluated by critics, audiences, or later literary traditions.
-
E.
literaryMovement
Indicates the artistic or intellectual movement in literature with which a work, author, or text is associated or to which it belongs.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 3, 2026, 4:13 p.m.