Triple
T34655205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sidus Iulium |
E889955
|
entity |
| Predicate | perceivedDuration |
P58344
|
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: [Sidus Iulium, perceivedDuration, several days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perceivedDuration Context triple: [Sidus Iulium, perceivedDuration, several days]
-
A.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
B.
timePerception
chosen
Indicates how an entity subjectively experiences, interprets, or estimates the passage and duration of time.
-
C.
showDuration
Indicates the length of time for which something is shown, displayed, or performed.
-
D.
durationDepicted
Indicates that a representation (such as a media item or depiction) specifies or conveys the length of time over which an event, process, or state occurs.
-
E.
actualDuration
Indicates the real amount of time that an event, process, or activity actually took to complete, as opposed to its planned or estimated duration.
- 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_69f349d906bc8190b2efd9eff237d94b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f72ad38a208190b4bdc828297f86ad |
completed | May 3, 2026, 11 a.m. |
| PD | Predicate disambiguation | batch_69f72a0243988190a43b8ea22457cd30 |
completed | May 3, 2026, 10:57 a.m. |
Created at: May 1, 2026, 2:04 a.m.