Triple
T9310882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saturnalia |
E224002
|
entity |
| Predicate | laterDuration |
P88010
|
FINISHED |
| Object | several days |
—
|
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: several days | Statement: [Saturnalia, laterDuration, several days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterDuration Context triple: [Saturnalia, laterDuration, several days]
-
A.
laterWithin
Indicates that one event or time point occurs later than another while still falling within a specified temporal interval or boundary.
-
B.
laterIn
Indicates that one event, state, or time point occurs after another in temporal order.
-
C.
alternativeDuration
Indicates that there is an additional or substitute time span associated with an event or activity, differing from its primary or standard duration.
-
D.
laterFrequency
Indicates that one event, state, or action occurs with a lower frequency than another in a temporal sequence.
-
E.
laterNumber
Indicates that one number occurs or is positioned later than another in a specified ordering or sequence.
- F. None of above. chosen
Provenance (4 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20ad3b20819092562c30e70a528f |
completed | April 1, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc955a38108190b602d1e73725f11b |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:37 p.m.