Triple
T25372311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linux /proc file system |
E632960
|
entity |
| Predicate | dataLifetime |
P93788
|
FINISHED |
| Object | data generated on demand |
—
|
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: data generated on demand | Statement: [Linux /proc file system, dataLifetime, data generated on demand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataLifetime Context triple: [Linux /proc file system, dataLifetime, data generated on demand]
-
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.
hasMeanLifetime
Indicates the characteristic average time duration for which an entity, state, or condition persists before it decays, ends, or changes.
-
D.
durationOfUse
Indicates the length of time for which something is used or remains in use.
-
E.
lifespanType
Indicates the type or category of lifespan associated with an entity, such as whether it is finite, indefinite, or of a particular defined 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:38 p.m.