Triple
T30334514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blitmap |
E771578
|
entity |
| Predicate | hasDigitalOwnershipModel |
P194185
|
FINISHED |
| Object | token-based ownership |
—
|
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: token-based ownership | Statement: [Blitmap, hasDigitalOwnershipModel, token-based ownership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDigitalOwnershipModel Context triple: [Blitmap, hasDigitalOwnershipModel, token-based ownership]
-
A.
hasDigitalAccess
Indicates that an entity has the ability or permission to use or access digital resources, services, or information.
-
B.
hasPopularDigitalVersionOn
Indicates that an entity has a widely used or well-known digital version available on a specified platform or medium.
-
C.
hasDigitalDistribution
Indicates that something is made available or delivered through electronic or online channels rather than through physical media.
-
D.
hasDigitalForm
Indicates that something exists or is available in a digital or electronic format.
-
E.
hasDigitalSystem
Indicates that an entity possesses, uses, or is equipped with a digital system (such as software, hardware, or an integrated digital platform).
- 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
| PDg | Predicate description generation | batch_69fd67182c348190aa84a02e08dbf4e1 |
completed | May 8, 2026, 4:31 a.m. |
Created at: April 29, 2026, 7:54 p.m.