Triple
T37235163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crypto.com Visa Card |
E923551
|
entity |
| Predicate | managingPlatform |
P34782
|
FINISHED |
| Object | Crypto.com App |
—
|
NE NERFINISHED |
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: Crypto.com App | Statement: [Crypto.com Visa Card, managingPlatform, Crypto.com App]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managingPlatform Context triple: [Crypto.com Visa Card, managingPlatform, Crypto.com App]
-
A.
platformsManaged
Indicates that one entity is responsible for overseeing, operating, or administering one or more platforms associated with another entity.
-
B.
managingCenter
Indicates that one entity serves as the administrative or coordinating center responsible for managing another entity or activity.
-
C.
deploymentPlatformType
Indicates the type or category of platform on which a deployment is executed or hosted.
-
D.
platformMate
Indicates that two entities are located on the same platform or share the same platform context at a given time.
-
E.
managementSoftware
chosen
Indicates that one entity is a software system used to organize, control, or coordinate the operations, resources, or processes of another entity.
- 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_69f76ea9fee88190a589f661d95a7189 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: May 3, 2026, 4:15 p.m.