Triple
T29014901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blueprint protocol |
E737276
|
entity |
| Predicate | publiclyDocumentedBy |
P192641
|
FINISHED |
| Object | Bryan Johnson |
—
|
NE NERFINISHED |
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: Bryan Johnson | Statement: [Blueprint protocol, publiclyDocumentedBy, Bryan Johnson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publiclyDocumentedBy Context triple: [Blueprint protocol, publiclyDocumentedBy, Bryan Johnson]
-
A.
documentedThrough
Indicates that something is recorded, evidenced, or made known by means of a specific document or documentation process.
-
B.
documentedUsing
Indicates that something is recorded, described, or specified by means of a particular document, tool, or documentation method.
-
C.
documentedFrom
Indicates that information about one entity is derived from, recorded in, or supported by another entity as its source of documentation.
-
D.
publiclyDisplayed
Indicates that something is shown or made visible in a public context or setting, accessible to people at large.
-
E.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
- F. None of above. chosen
Provenance (4 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_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
| PDg | Predicate description generation | batch_69fd231bdd108190900369e07c854e95 |
completed | May 7, 2026, 11:41 p.m. |
Created at: April 28, 2026, 9:45 a.m.