Triple
T15448732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TEMPORA |
E370092
|
entity |
| Predicate | storageDuration |
P93788
|
FINISHED |
| Object | up to 3 days for content |
—
|
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: up to 3 days for content | Statement: [TEMPORA, storageDuration, up to 3 days for content]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storageDuration Context triple: [TEMPORA, storageDuration, up to 3 days for content]
-
A.
dataRetentionPeriod
chosen
Indicates the length of time data is stored or kept before it is deleted, archived, or otherwise disposed of.
-
B.
existencePeriod
Indicates the time span during which an entity exists or is valid.
-
C.
storageOption
Indicates how or where something is stored, specifying the chosen method, medium, or configuration for its storage.
-
D.
storageProperty
Indicates a relationship where an entity has a specific storage-related characteristic, such as capacity, type, or configuration.
-
E.
canBeStoredFor
Indicates that something is suitable or allowed to be kept in storage for a certain duration or under certain conditions.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ef9334c81908541e231b43eb012 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:21 a.m.