Triple
T9029529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitcoin Cash |
E216132
|
entity |
| Predicate | hasIndependentDevelopmentTeams |
P7450
|
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, hasIndependentDevelopmentTeams, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndependentDevelopmentTeams Context triple: [Bitcoin Cash, hasIndependentDevelopmentTeams, true]
-
A.
hasIndependentTeams
chosen
Indicates that an entity possesses or is associated with teams that operate autonomously from other teams or central control.
-
B.
independentlyDevelopedBy
Indicates that something was created or developed by an entity without collaboration, influence, or shared effort with others.
-
C.
hasDevelopmentOrganization
Indicates that an entity is associated with, managed by, or supported by a specific organization responsible for its development.
-
D.
hasDevelopmentStudioIn
Indicates that an entity has a development studio located in a specified place.
-
E.
alsoDevelopedIn
Indicates that something was additionally developed in another context, location, or environment beyond the primary one already specified.
- 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_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:08 p.m.