Triple
T7899352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P2PKH |
E183408
|
entity |
| Predicate | standardness |
P41831
|
FINISHED |
| Object | standard output in Bitcoin Core policy |
—
|
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: standard output in Bitcoin Core policy | Statement: [P2PKH, standardness, standard output in Bitcoin Core policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardness Context triple: [P2PKH, standardness, standard output in Bitcoin Core policy]
-
A.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
B.
standardWithin
chosen
Indicates that one entity conforms to, or falls within the limits of, a specified standard defined by another entity.
-
C.
isStandardOf
Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
-
D.
standardApplied
Indicates that a particular standard, rule, or guideline has been put into effect or used as the basis for an action or decision in the relationship.
-
E.
standardReference
Indicates that one entity serves as the authoritative or canonical reference or benchmark for interpreting, validating, or comparing another entity.
- 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.