Triple
T34142503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hypomnemata |
E875755
|
entity |
| Predicate | survivalMode |
P21744
|
FINISHED |
| Object | fragments in later authors |
—
|
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: fragments in later authors | Statement: [Hypomnemata, survivalMode, fragments in later authors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivalMode Context triple: [Hypomnemata, survivalMode, fragments in later authors]
-
A.
survivalTheme
Indicates that the relationship or situation centers on the struggle to stay alive or endure extreme hardship.
-
B.
survivingUse
Indicates that one entity continues to make use of another entity or resource after an event that could have ended or invalidated that use.
-
C.
survivesIn
chosen
Indicates that an entity remains alive, functional, or intact within a specified environment, condition, or context.
-
D.
survivesExpedition
Indicates that an entity endures and remains alive through the duration of a specified expedition or journey.
-
E.
survivesFor
Indicates that one entity continues to exist, endure, or remain functional for a specified duration or period.
- 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_69f349aaeef08190a20e72a3fdeb7052 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:54 a.m.