Triple
T29014855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blueprint (longevity project) |
E737275
|
entity |
| Predicate | claimsToOptimize |
P13226
|
FINISHED |
| Object | overall health |
—
|
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: overall health | Statement: [Blueprint (longevity project), claimsToOptimize, overall health]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimsToOptimize Context triple: [Blueprint (longevity project), claimsToOptimize, overall health]
-
A.
claimsToBe
Indicates that one entity asserts or declares itself to have a particular identity, role, or property, regardless of whether this assertion is true.
-
B.
claimsToImprove
chosen
Indicates that one entity asserts or promises that it will enhance, benefit, or make another entity better in some way.
-
C.
claimsToEliminate
Indicates that one entity asserts it will remove, eradicate, or put an end to another entity or condition.
-
D.
claimsToMark
Indicates that one entity asserts or alleges that it has marked, labeled, or designated another entity in some specified way.
-
E.
claimsToExplain
Indicates that one entity asserts it can provide a clarification, account, or understanding of another entity or phenomenon.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 28, 2026, 9:45 a.m.