Triple
T36796919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LinkedIn Stories |
E909206
|
entity |
| Predicate | contentLifetime |
P191050
|
FINISHED |
| Object | 24 hours |
—
|
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: 24 hours | Statement: [LinkedIn Stories, contentLifetime, 24 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contentLifetime Context triple: [LinkedIn Stories, contentLifetime, 24 hours]
-
A.
contentDuration
chosen
Indicates the length of time for which the content runs or remains valid (e.g., its playback or availability duration).
-
B.
hasMeanLifetime
Indicates the characteristic average time duration for which an entity, state, or condition persists before it decays, ends, or changes.
-
C.
existencePeriod
Indicates the time span during which an entity exists or is valid.
-
D.
lifespanClaim
Indicates that there is a stated or asserted duration of existence (lifespan) associated with an entity.
-
E.
hasLifeSpan
Indicates that an entity is associated with a specific duration or range of time during which it remains alive or exists.
- 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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:12 p.m.