Triple
T30311057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act III of Tosca |
E770923
|
entity |
| Predicate | settingHistoricalPeriod |
P93599
|
FINISHED |
| Object | Napoleonic era |
—
|
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: Napoleonic era | Statement: [Act III of Tosca, settingHistoricalPeriod, Napoleonic era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingHistoricalPeriod Context triple: [Act III of Tosca, settingHistoricalPeriod, Napoleonic era]
-
A.
settingDepictedPeriod
chosen
Indicates the historical or temporal period in which the setting of something (e.g., a work or scene) is depicted.
-
B.
historicalPeriodOfSignificance
Indicates the time period during which an entity is considered to have had its most important or influential historical impact.
-
C.
historicalIntroductionPeriod
Indicates the time period during which something was first introduced or came into use in a historical context.
-
D.
historicalDocumentationPeriod
Indicates the time span during which something is documented or recorded in historical sources.
-
E.
historical era
Indicates the broad historical period or epoch during which an entity, event, or phenomenon took place or is associated.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 29, 2026, 7:50 p.m.