Triple
T11556870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Brevitate Vitae |
E274038
|
entity |
| Predicate | hasModernRelevanceFor |
P82904
|
FINISHED |
| Object | time management discourse |
—
|
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: time management discourse | Statement: [De Brevitate Vitae, hasModernRelevanceFor, time management discourse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernRelevanceFor Context triple: [De Brevitate Vitae, hasModernRelevanceFor, time management discourse]
-
A.
hasModernRelevance
chosen
Indicates that something maintains significance, applicability, or impact in contemporary times or current contexts.
-
B.
hasContemporaryRecognition
Indicates that an entity is currently acknowledged, honored, or widely recognized in the present time or modern era.
-
C.
notableModernIssue
Indicates that the subject is recognized as a significant or widely discussed issue in contemporary times.
-
D.
hasViewOnModernity
Indicates that an entity holds a particular perspective, stance, or interpretation regarding modernity.
-
E.
hasModernRepresentatives
Indicates that an entity has current or contemporary examples, members, or instances that represent it in the modern era.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88a86be308190973fea5d7db8ba9d |
completed | April 10, 2026, 5:28 a.m. |
| PD | Predicate disambiguation | batch_69d85dc3fc2c8190bed7e2111301a77c |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:37 p.m.