Triple
T38394974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Godunoff |
E900730
|
entity |
| Predicate | timeOfProminentUsage |
P122700
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Godunoff, timeOfProminentUsage, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfProminentUsage Context triple: [Godunoff, timeOfProminentUsage, 19th century]
-
A.
firstProminentlyUsedAfter
Indicates that one entity began to be widely or notably used only after the time or event associated with another entity.
-
B.
firstProminentUse
Indicates the earliest notable or widely recognized instance in which something was used in a significant or influential way.
-
C.
periodOfMajorUse
Indicates the time span during which something was primarily or most intensively used.
-
D.
historicalPeriodOfGreatestUse
chosen
Indicates the time period during which something was used most intensively or prevalently.
-
E.
firstWidelyUsedDuring
Indicates that something (such as a concept, technology, or practice) came into its first period of broad or widespread use during a specified time or era.
- 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe72dca2f08190beff17de3d2aada6 |
completed | May 8, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69fe70bca8d08190b810e1e616ceac44 |
completed | May 8, 2026, 11:24 p.m. |
Created at: May 3, 2026, 4:31 p.m.