Triple
T37520735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Life of William Congreve |
E932764
|
entity |
| Predicate | biographicalSubjectEra |
P117687
|
FINISHED |
| Object | Restoration period |
—
|
NE NERFINISHED |
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: Restoration period | Statement: [Life of William Congreve, biographicalSubjectEra, Restoration period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biographicalSubjectEra Context triple: [Life of William Congreve, biographicalSubjectEra, Restoration period]
-
A.
depictedPersonEra
Indicates the historical era or time period associated with the person depicted in an image or representation.
-
B.
livedInEra
chosen
Indicates that an entity existed or was active during a particular historical era or time period.
-
C.
historical era
Indicates the broad historical period or epoch during which an entity, event, or phenomenon took place or is associated.
-
D.
associatedWithNotableEra
Indicates that something has a significant connection or relevance to a historically or culturally notable period of time.
-
E.
historicalEraUsheredIn
Indicates the historical era or period that was initiated or brought about as a result of a particular event, action, or 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.