Triple
T8487930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryan Johnson |
E200877
|
entity |
| Predicate | BraintreeIndustry |
P11670
|
FINISHED |
| Object | online payments |
—
|
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: online payments | Statement: [Bryan Johnson, BraintreeIndustry, online payments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BraintreeIndustry Context triple: [Bryan Johnson, BraintreeIndustry, online payments]
-
A.
canBeMadeCCAsecureBy
Indicates that one cryptographic scheme or construction can be transformed or augmented to achieve chosen-ciphertext attack (CCA) security by using another scheme, technique, or component.
-
B.
paymentEnvironment
chosen
Indicates the context or setting in which a payment is initiated, processed, or completed (such as online, in-store, or in-app).
-
C.
paymentDomain
Indicates the domain, context, or scope within which a payment is applicable, processed, or governed.
-
D.
paymentServices
Indicates that one entity provides or facilitates payment-related services or processing for another entity.
-
E.
commercePower
Indicates the authority or capacity to regulate, control, or influence commercial transactions or trade activities.
- 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe556b5188190b1124effd7445803 |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:13 p.m.