Triple
T9029515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitcoin Cash |
E216132
|
entity |
| Predicate | openSourceSoftware |
P25429
|
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, openSourceSoftware, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openSourceSoftware Context triple: [Bitcoin Cash, openSourceSoftware, true]
-
A.
openSource
Indicates that the subject makes its source code publicly available under a license that allows others to use, modify, and redistribute it.
-
B.
openSourceProject
chosen
Indicates that the subject is a software project whose source code is publicly available and can be used, modified, and redistributed under an open-source license.
-
C.
openSourceAttempt
Indicates an attempt or effort by an entity to make something open source, such as releasing code or resources under an open-source license.
-
D.
supportsOpenSource
Indicates that one entity actively endorses, contributes to, or otherwise promotes open-source software or open-source initiatives.
-
E.
softwareFreedomStatus
Indicates the degree to which a piece of software respects users’ freedoms to use, study, modify, and share it.
- 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_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. |
Created at: March 30, 2026, 7:08 p.m.