Triple
T24202054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | opera seria |
E600006
|
entity |
| Predicate | hasDeclinePeriod |
P32954
|
FINISHED |
| Object | late 18th 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: late 18th century | Statement: [opera seria, hasDeclinePeriod, late 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeclinePeriod Context triple: [opera seria, hasDeclinePeriod, late 18th century]
-
A.
declineBeganInPeriod
chosen
Indicates that the onset of a decline in the subject occurred during the specified time period.
-
B.
declinedDuring
Indicates that one entity’s value, condition, or status decreased over the course of a specified time period or event.
-
C.
endedOrDeclinedAfter
Indicates that one entity’s involvement, status, or offer concluded or was rejected following the occurrence or completion of another specified event or condition.
-
D.
refusalPeriodMaximum
Indicates the maximum allowed duration within which a refusal can occur or remain valid in the context of the related relationship or action.
-
E.
declinedAround
Indicates that something decreased in value, intensity, or quantity in the time period surrounding a specified point or event.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca1f3b481908c14052a8435fd21 |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:36 p.m.