Triple
T7899321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P2PKH |
E183408
|
entity |
| Predicate | requiresToSpend |
P100
|
FINISHED |
| Object | public key |
—
|
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: public key | Statement: [P2PKH, requiresToSpend, public key]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresToSpend Context triple: [P2PKH, requiresToSpend, public key]
-
A.
requiresPaymentOf
Indicates that one entity obligates another entity to provide a specified payment as a condition or requirement.
-
B.
requiredPledgeFrom
Indicates that one entity mandates or demands a pledge or commitment from another entity as a prerequisite or condition.
-
C.
requiresBalanceWith
Indicates that one entity’s state, quantity, or action must be countered or matched by another to maintain an overall balance or equilibrium.
-
D.
requires
chosen
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
E.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
- 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_69ca828d13088190b222be7aa9f9315c |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a3dc2208190a6fea93b60b8daca |
completed | March 31, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69cae92d94448190b4425bbfb64c658c |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:01 p.m.