Triple
T30407364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitcoin Cash |
E773514
|
entity |
| Predicate | isCensorshipResistant |
P170217
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bitcoin Cash, isCensorshipResistant, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCensorshipResistant Context triple: [Bitcoin Cash, isCensorshipResistant, true]
-
A.
censorshipLevel
Indicates the degree or strictness of control, suppression, or restriction applied to information, media, or expression.
-
B.
censorshipAuthority
Indicates that one entity has the official power or responsibility to censor, restrict, or approve the information, media, or expression of another entity.
-
C.
censorshipCertificate
Indicates that an entity has been reviewed by an authority and granted an official certificate confirming it has passed censorship or content regulation requirements.
-
D.
typeOfCensorship
Indicates the specific kind or method of censorship being applied in a given context.
-
E.
censoredSetting
Indicates that a setting or environment has been modified to restrict, remove, or obscure certain content or information.
- 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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68b121eac81909e90416207bc1157 |
completed | May 2, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f68a160374819084d720985f800dfc |
completed | May 2, 2026, 11:34 p.m. |
Created at: April 29, 2026, 8:04 p.m.