Triple
T19083141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian Rosenkreuz |
E467078
|
entity |
| Predicate | lifespanInLegend |
P585
|
FINISHED |
| Object | 106 years |
—
|
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: 106 years | Statement: [Christian Rosenkreuz, lifespanInLegend, 106 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifespanInLegend Context triple: [Christian Rosenkreuz, lifespanInLegend, 106 years]
-
A.
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.
-
B.
lifespan
chosen
Indicates the duration of time between an entity’s birth (or creation) and its death (or end).
-
C.
sourceForLifespan
Indicates that one entity serves as the reference or authority providing information about the lifespan of another entity.
-
D.
documentedLifePeriodOf
Indicates that a described or recorded time span pertains to, or represents, a specific period in an entity’s life.
-
E.
supportsLifespan
Indicates that one entity contributes to maintaining, extending, or enabling the full duration of another entity’s life or functional existence.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2eab58c8190a987c88d633c92ec |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.