Triple
T7899329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P2PKH |
E183408
|
entity |
| Predicate | scriptSigContains |
P79660
|
FINISHED |
| Object | signature |
—
|
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: signature | Statement: [P2PKH, scriptSigContains, signature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptSigContains Context triple: [P2PKH, scriptSigContains, signature]
-
A.
requiresSignatureOf
Indicates that one entity must obtain or depend on the formal signature or signed approval of another entity.
-
B.
hasSignaturePhrase
Indicates that an entity (such as a person or character) is associated with a distinctive, repeatedly used phrase that is characteristically theirs.
-
C.
isSignatureHitFor
Indicates that one event, action, or data pattern matches and triggers a specific predefined signature (such as a rule, template, or detection pattern).
-
D.
containsScript
Indicates that one entity includes or embeds the script of another entity within it.
-
E.
isCodeForUndecipheredScript
Indicates that something serves as a code or encoding system used to represent an undeciphered script.
- 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_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. |
| PDg | Predicate description generation | batch_69caf7882b048190baa333af9f698590 |
completed | March 30, 2026, 10:22 p.m. |
Created at: March 30, 2026, 5:01 p.m.