Triple
T9029516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitcoin Cash |
E216132
|
entity |
| Predicate | supportsReplayProtection |
P85976
|
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, supportsReplayProtection, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsReplayProtection Context triple: [Bitcoin Cash, supportsReplayProtection, true]
-
A.
usesInstantReplay
Indicates that an entity employs instant replay technology or review during an event, action, or decision process.
-
B.
supportsBalanceProtection
Indicates that an entity provides or enables a balance protection feature that safeguards an account’s or position’s value against certain losses or negative changes.
-
C.
replayedOn
Indicates that an event, performance, or recording was played again on a particular medium, platform, or channel.
-
D.
supportsInstantPlay
Indicates that one entity enables or is compatible with immediate, on-demand use or playback of another entity without requiring prior download or installation.
-
E.
previousProtectionStatus
Indicates the protection or security state an entity was in before its current protection status.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a9bcb508190b58751f1772407d4 |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f887108819096d45a186fc137b3 |
completed | March 31, 2026, 11:58 p.m. |
Created at: March 30, 2026, 7:08 p.m.