Triple
T30573820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nilovna |
E778188
|
entity |
| Predicate | timeOfLiteraryUse |
P142886
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Nilovna, timeOfLiteraryUse, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfLiteraryUse Context triple: [Nilovna, timeOfLiteraryUse, early 20th century]
-
A.
firstMajorLiteraryUseDate
Indicates the date when something was first significantly used or attested in major literary works.
-
B.
timeOfMajorLiteraryFormulation
chosen
Indicates the time period during which a major or definitive literary formulation of something was created or established.
-
C.
literaryUse
Indicates that something is employed or referenced within a literary context, such as in a written work, style, or technique.
-
D.
literaryPeriodOfReception
Indicates the historical literary period during which a work was primarily received, interpreted, or influential.
-
E.
activeYearsInLiterature
Indicates the span of years during which an entity was actively producing or contributing to literary works.
- 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 29, 2026, 8:22 p.m.